This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 3/3] Use command "monitor set debug 0" to check the connection
- From: Yao Qi <yao at codesourcery dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Thu, 9 Oct 2014 11:01:20 +0800
- Subject: Re: [PATCH 3/3] Use command "monitor set debug 0" to check the connection
- Authentication-results: sourceware.org; auth=none
- References: <543404EF dot 4010306 at redhat dot com> <1412749679-27076-1-git-send-email-yao at codesourcery dot com> <1412749679-27076-4-git-send-email-yao at codesourcery dot com> <543547FC dot 30306 at redhat dot com>
Pedro Alves <palves@redhat.com> 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:
Packet qTStatus (trace-status) is NOT supported
...
(gdb) show remote trace-status-packet
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) == PACKET_DISABLE)
return -1;
so no RSP packet is sent out.
(gdb) set debug remote 1
(gdb) tstatus
Trace can not be run on this target.
--
Yao (éå)