From: Richard <rgrdev@googlemail.com>
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 07:27:00 -0000 [thread overview]
Message-ID: <8764h38z7m.fsf@mail.com> (raw)
In-Reply-To: <20060808000358.GA744@nevyn.them.org> (Daniel Jacobowitz's message of "Mon, 7 Aug 2006 20:03:58 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> On Mon, Aug 07, 2006 at 11:47:03PM +0200, Richard wrote:
>> set follow-fork-mode to both is not supported:
>
> Sorry, try turning off detach-on-fork. See "help set".
>
>> Sorry, if I'm missing something obvious. How owuld I browse "recent
>> features" in CVS?
>
> Take a look at the NEWS file.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>
I tried setting detach-on-fork to off and follow-fork to "child" and it
all just froze. Possibly I'm misunderstanding its use?
Could you advise on its intended use and how it integrates with
follow-fork-mode or catch fork? I set follow to "child", detach to "off"
and then "info fork" reported no forks after the fork() call while in
the childs code.
"both" is now removed for "follow-fork"?
next prev parent reply other threads:[~2006-08-08 7:27 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 [this message]
2006-08-08 8:49 ` Richard
2006-08-08 13:16 ` Daniel Jacobowitz
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=8764h38z7m.fsf@mail.com \
--to=rgrdev@googlemail.com \
--cc=gdb@sources.redhat.com \
--cc=rgrdev@gmail.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