This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
server/2288: linux gdbserver does not detect when suspended child dies with SIGKILL
- From: michael dot snyder at access-company dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 17 Jul 2007 21:51:19 -0000
- Subject: server/2288: linux gdbserver does not detect when suspended child dies with SIGKILL
- Reply-to: michael dot snyder at access-company dot com
>Number: 2288
>Category: server
>Synopsis: linux gdbserver does not detect when suspended child dies with SIGKILL
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jul 17 21:58:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator: Michael Snyder
>Release: 6.6
>Organization:
>Environment:
remote gdbserver
>Description:
If the child is running and receives SIGKILL, gdbserver catches it successfully. But if the child is stopped eg. for a breakpoint (gdb is at the prompt), and SIGKILL is sent to the child, the child dies immediately but gdbserver does not detect the fact. If gdb then tries to continue, gdbserver prints some warnings but still does not bail out, and gdb hangs.
>How-To-Repeat:
target remote
stop at breakpoint
telnet to the target system
kill -9 <child-pid>
(gdb) continue
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: