This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/923: Stepping over a fork call in gdb causes child process to become a zombie
- From: mark at streamline-computing dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 10 Jan 2003 16:24:39 -0000
- Subject: gdb/923: Stepping over a fork call in gdb causes child process to become a zombie
- Reply-to: mark at streamline-computing dot com
>Number: 923
>Category: gdb
>Synopsis: Stepping over a fork call in gdb causes child process to become a zombie
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jan 10 08:28:14 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Mark
>Release: 5.2
>Organization:
>Environment:
Linux Redhat 7.3
>Description:
Stepping over a fork call in gdb causes child process to become a zombie. It seems this bug has been spotted before(http://developer.axis.com/doc/software/tools/gdb/knownproblems.html) but I can find no mention of it in this database.
>How-To-Repeat:
Compile up a program containing a call to fork(), and then use gdb to step over the fork() call (using the 'next' command for example). The child process is created but zombied. This doesn't happen if you put a breakpoint on the next line and use continue to execute the fork() call.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: