From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9024 invoked by alias); 9 Oct 2014 03:05:35 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 9012 invoked by uid 89); 9 Oct 2014 03:05:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 09 Oct 2014 03:05:32 +0000 Received: from svr-orw-fem-04.mgc.mentorg.com ([147.34.97.41]) by relay1.mentorg.com with esmtp id 1Xc42i-0007Qk-Q8 from Yao_Qi@mentor.com ; Wed, 08 Oct 2014 20:05:28 -0700 Received: from GreenOnly (147.34.91.1) by svr-orw-fem-04.mgc.mentorg.com (147.34.97.41) with Microsoft SMTP Server id 14.3.181.6; Wed, 8 Oct 2014 20:05:28 -0700 From: Yao Qi To: Pedro Alves CC: Subject: Re: [PATCH 3/3] Use command "monitor set debug 0" to check the connection References: <543404EF.4010306@redhat.com> <1412749679-27076-1-git-send-email-yao@codesourcery.com> <1412749679-27076-4-git-send-email-yao@codesourcery.com> <543547FC.30306@redhat.com> Date: Thu, 09 Oct 2014 03:05:00 -0000 In-Reply-To: <543547FC.30306@redhat.com> (Pedro Alves's message of "Wed, 8 Oct 2014 15:19:40 +0100") Message-ID: <87zjd6rlof.fsf@codesourcery.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2014-10/txt/msg00178.txt.bz2 Pedro Alves writes: > That error is printed by trace_status_command, but only after calling > target_get_trace_status, which seems to me should be sending a packet. > > remote_get_trace_status's exception swallowing should be > letting TARGET_CLOSE_ERROR pass through. Is that not working? > I'm a bit confused because it seems like if that didn't work, > we should see a "qTStatus:..." error line in the logs. > > So what is preventing the packet from being sent? qTStatus is disabled after receiving the empty reply during connecting to the remote target. (gdb) set debug remote 1 (gdb) target remote :4444 ... Sending packet: $qTStatus#49...Packet received:=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20 Packet qTStatus (trace-status) is NOT supported ... (gdb) show remote trace-status-packet=20 Support for the `qTStatus' packet is auto-detected, currently disabled. When the test executes command "tstatus" again, remote_get_trace_status returns -1 at the very beginning, if (packet_support (PACKET_qTStatus) =3D=3D PACKET_DISABLE) return -1; so no RSP packet is sent out. (gdb) set debug remote 1 (gdb) tstatus=20 Trace can not be run on this target. --=20 Yao (=E9=BD=90=E5=B0=A7)