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

[Yao Qi <yao@codesourcery.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 (齐尧)