This is the mail archive of the
mailing list for the Cygwin project.
Re: Debugging sub-processes with gdb
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 14 May 2014 11:25:05 -0400
- Subject: Re: Debugging sub-processes with gdb
- Authentication-results: sourceware.org; auth=none
- References: <f5boaz0e6qb dot fsf at troutbeck dot inf dot ed dot ac dot uk>
- Reply-to: cygwin at cygwin dot com
On Wed, May 14, 2014 at 04:10:36PM +0100, Henry S. Thompson wrote:
>I'm trying to debug a problem with xemacs that involves the child
>process forked when you execute M-x shell.
>None of the mechanisms in the gdb documentation for choosing to step
>into the child process (instead of the parent) after a fork() seem to
>work for me. That is, in particular, setting follow-for-mode to child
>still leaves me in the parent after stepping over a fork().
>Setting detach-on-fork to 'off' also seems to have no effect.
>Have I misunderstood something, or does this aspect of gdb just not
>work under cygwin (x86_64, 1.7.29-2)?
Debugging subprocesses doesn't work for Windows gdb. Sorry.
If you have control over the code you could have it print a pid, wait,
and then attach to it with gdb. That works.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple