From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>,
Randolph Chung <tausq@debian.org>
Subject: Re: [RFA] linux multi-fork kill (re: "run", and executable file/symtab association?)
Date: Sat, 11 Mar 2006 11:39:00 -0000 [thread overview]
Message-ID: <20060310200839.GA30634@nevyn.them.org> (raw)
In-Reply-To: <4410D0AC.1000505@redhat.com>
On Thu, Mar 09, 2006 at 05:04:44PM -0800, Michael Snyder wrote:
> Randolph, this is in response to your bug report.
> Daniel, see if this looks OK to you. Instead of calling
> pop_target (which, I agree, was iffy), we just go thru
> target_mourn_inferior like we always did.
>
> Rearranged linux_fork_killall because of an unexpected
> interaction with delete_fork -- at least one fork wasn't
> getting killed, because delete_fork tries to be too clever.
Looks good to me. You're right, I'll need to re-merge - how about
you go first since I don't know when I'll have a chance to update
that patch?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-10 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 2:11 Michael Snyder
2006-03-11 11:39 ` Daniel Jacobowitz [this message]
2006-03-11 19:08 ` 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=20060310200839.GA30634@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@redhat.com \
--cc=tausq@debian.org \
/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