aboutsummaryrefslogtreecommitdiff
path: root/gdb/value.h
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@gnat.com>2010-07-07 16:14:04 +0000
committerJoel Brobecker <brobecker@gnat.com>2010-07-07 16:14:04 +0000
commit6bd31874685a739404578403651d7b1ad5d20a3e (patch)
tree547eace37b15788ae0840c2d945110e5301a62f0 /gdb/value.h
parent2f2241f14651e177f430128c5d22755628a7d91d (diff)
downloadgdb-6bd31874685a739404578403651d7b1ad5d20a3e.zip
gdb-6bd31874685a739404578403651d7b1ad5d20a3e.tar.gz
gdb-6bd31874685a739404578403651d7b1ad5d20a3e.tar.bz2
[PATCH] Unexpected EOF read from connection with GDB after inferior exits.
This is on GNU/Linux. GDBserver does not exit properly when the inferior exits, as demonstrated with any program using the procedure below: % gdbserver-head :4444 simple_main Process simple_main created; pid = 25681 Listening on port 4444 Then, in another terminal, start GDB, connect to GDBserver, and run the program to completion: % gdb-head simple_main (gdb) tar rem :4444 (gdb) cont Continuing. Program exited normally. Going back to the terminal where GDBserver is running, we see the following output: Child exited with status 0 readchar: Got EOF Remote side has terminated connection. GDBserver will reopen the connection. Listening on port 4444 The problem is that we're missing a call to mourn_inferior. As a result, after we've handled the vCont packet, we fail to notice that there are no process left to debug (target_running() returns true), and thus try to continue reading from the remote socket. However, since GDB just disconnected after having received the "exit with status 0" reply to the vCont request, the read triggers the EOF exception. gdb/gdbserver/ChangeLog: * server.c (handle_v_cont): Call mourn_inferior if process just exited. (myresume): Likewise.
Diffstat (limited to 'gdb/value.h')
0 files changed, 0 insertions, 0 deletions