public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ht@inf.ed.ac.uk (Henry S. Thompson)
To: cygwin@cygwin.com
Subject: Re: Debugging sub-processes with gdb
Date: Wed, 14 May 2014 16:52:00 -0000	[thread overview]
Message-ID: <f5bk39oe5ic.fsf@troutbeck.inf.ed.ac.uk> (raw)
In-Reply-To: <20140514152505.GB6620@ednor.casa.cgf.cx> (Christopher Faylor's message of "Wed\, 14 May 2014 11\:25\:05 -0400")

Christopher Faylor writes:

> 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.

Thanks for confirming.

> If you have control over the code you could have it print a pid, wait,
> and then attach to it with gdb.  That works.

Understood, will do.

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
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

  parent reply	other threads:[~2014-05-14 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 15:25 Henry S. Thompson
2014-05-14 15:26 ` Christopher Faylor
2014-05-14 15:37   ` LRN
2014-05-14 16:52   ` Henry S. Thompson [this message]
2014-05-14 18:00     ` Christopher Faylor
2014-05-14 15:34 ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f5bk39oe5ic.fsf@troutbeck.inf.ed.ac.uk \
    --to=ht@inf.ed.ac.uk \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).