Re: [PATCH 3/3] Use command "monitor set debug 0" to check the connection

[Pedro Alves <palves@redhat.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