From: Pedro Alves <pedro@codesourcery.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix foll-fork.exp foll-vfork.exp fork-child-threads.exp
Date: Fri, 21 Nov 2008 02:09:00 -0000 [thread overview]
Message-ID: <200811201652.35125.pedro@codesourcery.com> (raw)
In-Reply-To: <200811201636.mAKGawpG029010@d12av02.megacenter.de.ibm.com>
On Thursday 20 November 2008 16:36:58, Ulrich Weigand wrote:
> Looks good to me, thanks.
Thanks. I'll check it in.
> As a separate question, I'm wondering why this is the right place to
> put the follow-fork logic anyway (and not in handle_inferior_event
> like follow-exec ...). Do you know the history of this?
To be able to decide if you want to follow a child or a parent
when you catch a fork with "catch fork".
There's nothing to decide to follow or not on a "catch exec", the
image has already been replaced when you get the event, so gdb must
load the new symbols before dropping to the user/cli.
--
Pedro Alves
next prev parent reply other threads:[~2008-11-20 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 19:15 Pedro Alves
2008-11-20 23:52 ` Ulrich Weigand
2008-11-21 1:35 ` Pedro Alves
2008-11-21 1:49 ` Ulrich Weigand
2008-11-21 2:09 ` Pedro Alves [this message]
2008-11-21 11:40 ` Ulrich Weigand
2008-11-21 12:58 ` Pedro Alves
2008-12-01 19:01 ` Michael Snyder
2008-12-01 20:56 ` Daniel Jacobowitz
2008-12-01 22:36 ` Michael Snyder
2008-12-01 21:06 ` Pedro Alves
2008-12-01 22:38 ` Michael Snyder
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=200811201652.35125.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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