diff options
| author | Yao Qi <yao@codesourcery.com> | 2014-10-08 11:25:31 +0800 |
|---|---|---|
| committer | Yao Qi <yao@codesourcery.com> | 2014-10-11 11:13:39 +0800 |
| commit | 754dd2b00f2bd3f2d7aaacdb27375bc6faf1458e (patch) | |
| tree | d387785f824df5ae374ad19f9e089fac4cbe69eb /libiberty | |
| parent | f90183d7e31b335b8a6048e46805509dc56332a4 (diff) | |
| download | gdb-754dd2b00f2bd3f2d7aaacdb27375bc6faf1458e.zip gdb-754dd2b00f2bd3f2d7aaacdb27375bc6faf1458e.tar.gz gdb-754dd2b00f2bd3f2d7aaacdb27375bc6faf1458e.tar.bz2 | |
Enable qTStatus packet in case it is disabled
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
qTStatus is disabled after receiving the empty reply during connecting
to the remote target. When the test executes command "tstatus" again,
remote_get_trace_status returns -1 at the very beginning, and no RSP
packet is sent out.
This patch is to enable qTStatus packet again.
gdb/testsuite:
2014-10-11 Yao Qi <yao@codesourcery.com>
* gdb.server/server-kill.exp: Execute command
"set remote trace-status-packet on" before "tstatus".
Diffstat (limited to 'libiberty')
0 files changed, 0 insertions, 0 deletions