From: Daniel Jacobowitz <drow@false.org>
To: Richard <rgrdev@googlemail.com>
Cc: Richard <rgrdev@gmail.com>, gdb@sources.redhat.com
Subject: Re: fork debugging : back to parent.
Date: Tue, 08 Aug 2006 13:16:00 -0000 [thread overview]
Message-ID: <20060808131653.GA16362@nevyn.them.org> (raw)
In-Reply-To: <87zmef393u.fsf@mail.com>
On Tue, Aug 08, 2006 at 10:49:41AM +0200, Richard wrote:
> By setting follow to parent and detach to off, one can use info fork in
> the parent thread in order to switch to the child thread.
>
> If follow is set to child and detach is off, then there is no fork info
> in the child for some reason so you cant switch back to the parent. Is
> this a bug?
Yes, this does sound like a bug.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-08 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 20:21 Richard (sent by Nabble.com)
2006-08-07 21:07 ` Daniel Jacobowitz
2006-08-07 21:47 ` Richard
2006-08-08 0:04 ` Daniel Jacobowitz
2006-08-08 7:27 ` Richard
2006-08-08 8:49 ` Richard
2006-08-08 13:16 ` Daniel Jacobowitz [this message]
2006-08-10 21:06 ` Richard
2006-08-10 21:39 ` Daniel Jacobowitz
2006-08-10 22:06 ` Richard
2006-08-10 22:10 ` Daniel Jacobowitz
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=20060808131653.GA16362@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=rgrdev@gmail.com \
--cc=rgrdev@googlemail.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