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".
This commit is contained in:
parent
f90183d7e3
commit
754dd2b00f
|
@ -1,3 +1,8 @@
|
|||
2014-10-11 Yao Qi <yao@codesourcery.com>
|
||||
|
||||
* gdb.server/server-kill.exp: Execute command
|
||||
"set remote trace-status-packet on" before "tstatus".
|
||||
|
||||
2014-10-11 Yao Qi <yao@codesourcery.com>
|
||||
|
||||
* gdb.server/server-kill.c: Include sys/types.h and unistd.h.
|
||||
|
|
|
@ -52,6 +52,11 @@ if {$server_pid == "" } {
|
|||
|
||||
remote_exec target "kill -9 $server_pid"
|
||||
|
||||
# Enable trace status packet which is disabled after the connection
|
||||
# if the remote target doesn't support tracepoint at all. Otherwise,
|
||||
# no RSP packet is sent out.
|
||||
gdb_test_no_output "set remote trace-status-packet on"
|
||||
|
||||
# Force GDB to talk with GDBserver, so that we can get the
|
||||
# "connection closed" error.
|
||||
gdb_test "tstatus" {Remote connection closed|Remote communication error\. Target disconnected\.: Connection reset by peer\.}
|
||||
|
|
Loading…
Reference in New Issue