From 5b37825d8476bc21cd2d78279481c0efc6b430c8 Mon Sep 17 00:00:00 2001 From: Philippe Waroquiers Date: Fri, 3 Feb 2012 22:52:32 +0000 Subject: The remote stub can implement monitor commands which are not known by gdb. Such monitor commands can take a long time to execute. An example of this is the "leak_search" monitor command implemented in the Valgrind gdbserver. Currently, gdb will timeout on such a monitor command. The remote stub however will continue to execute the command and send the output later. Gdb and the remote stub can then be desynchronised : gdb sends a packet, and the reply read from the stub is a previous packet. The change committed uses getpkt_sane to detect a timeout. In this case, it continues the loop. A QUIT; is inserted in the loop to allow the user to stop handling the current command. possibly still creating a desynchronisation between gdb and the stub but that will be upon user request. --- gdb/ChangeLog | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'gdb/ChangeLog') diff --git a/gdb/ChangeLog b/gdb/ChangeLog index ddef913..9fb261a 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2012-02-03 Philippe Waroquiers + + * remote.c (remote_rcmd): Use getpkt_sane to detect timeout + and continue the loop. Add QUIT statement. + 2012-02-03 Tom Tromey PR gdb/13596: -- cgit v1.1