diff options
author | Nicholas Duffek <nsd@redhat.com> | 2000-04-05 02:26:37 +0000 |
---|---|---|
committer | Nicholas Duffek <nsd@redhat.com> | 2000-04-05 02:26:37 +0000 |
commit | 2364aacb864bc3bc98f4cc927efe3186b075c3e2 (patch) | |
tree | 576a1b1a2dfad0d88d3e27970d8baa7f507cc0a7 /gdb/infrun.c | |
parent | e5741648b1f754825c4b3d412dddb67140707874 (diff) | |
download | gdb-2364aacb864bc3bc98f4cc927efe3186b075c3e2.tar.gz |
* infrun.c (handle_inferior_event): Call target_mourn_inferior
instead of kill_target.
Diffstat (limited to 'gdb/infrun.c')
-rw-r--r-- | gdb/infrun.c | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/gdb/infrun.c b/gdb/infrun.c index 6bc32d803be..594523f1716 100644 --- a/gdb/infrun.c +++ b/gdb/infrun.c @@ -1555,12 +1555,12 @@ handle_inferior_event (struct execution_control_state *ecs) stop_signal = ecs->ws.value.sig; target_terminal_ours (); /* Must do this before mourn anyway */ - /* This looks pretty bogus to me. Doesn't TARGET_WAITKIND_SIGNALLED - mean it is already dead? This has been here since GDB 2.8, so - perhaps it means rms didn't understand unix waitstatuses? - For the moment I'm just kludging around this in remote.c - rather than trying to change it here --kingdon, 5 Dec 1994. */ - target_kill (); /* kill mourns as well */ + /* Note: By definition of TARGET_WAITKIND_SIGNALLED, we shouldn't + reach here unless the inferior is dead. However, for years + target_kill() was called here, which hints that fatal signals aren't + really fatal on some systems. If that's true, then some changes + may be needed. */ + target_mourn_inferior (); print_stop_reason (SIGNAL_EXITED, stop_signal); singlestep_breakpoints_inserted_p = 0; /*SOFTWARE_SINGLE_STEP_P */ |