X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=ptSeZuk1tEdPmhR76Q0mN2AhqbOpwRlOpM6tKYvjiRGypuCwsZHNj
	ABbfHrNfyM5aLu/iTYCjHrDurxudvX0wqb+Q99A55ETfLKqOLlii/YnP+0hpx1u2
	2I9Xr4xeaXYJ/il0osbeAUSIlwFQwfjzMNMCsAeGShTxwaRwJxLt4Q=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=TchRcwRnhAVFSdQPU+QO7WDjH+8=; b=dzMPaVUysviajeBOCq2wR+KsgqAz
	qSWvKoo8DnguiaSVqfCyyf0Mv+MOcRgtWEuQ30ZHeSahuxGV48Gmmz1LaSlHdykJ
	T20NmvS03tw4EKI717sXd0RA7TsN+ljMI9Ua/CIcXRS3VimD2Jn+j6xznjZT+bNI
	bFG+Zo8TDhMo9EE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-01-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+nA5fMW1NHPXBrBpwAj9cD
Date: Wed, 14 May 2014 11:25:05 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Debugging sub-processes with gdb
Message-ID: <20140514152505.GB6620@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <f5boaz0e6qb DOT fsf AT troutbeck DOT inf DOT ed DOT ac DOT uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f5boaz0e6qb.fsf@troutbeck.inf.ed.ac.uk>
User-Agent: Mutt/1.5.20 (2009-06-14)

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.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple