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: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Wed, 08 Oct 2014 15:19:40 +0100
- 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>
On 10/08/2014 07:27 AM, Yao Qi wrote:
> Nowadays, we are using command "tstatus" to send a packet to GDBserver
> in order to check the connection. However, on the target doesn't
> support tracepoint, the following error is emitted before sending any
> packet to GDBserver.
>
> tstatus^M
> Trace can not be run on this target.^M
> (gdb) FAIL: gdb.server/server-kill.exp: tstatus
>
> We have to choose other commands which exists on different targets, and
> send a RSP packet to GDBserver. "monitor set debug 0" is a good one.
>
Hmm, are you sure GDB didn't really send any packet to GDBserver?
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?
Thanks,
Pedro Alves