From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Async patch (no. 3)
Date: Fri, 13 Oct 2006 13:11:00 -0000 [thread overview]
Message-ID: <20061013131118.GA8144@nevyn.them.org> (raw)
In-Reply-To: <17711.20298.658015.189122@kahikatea.snap.net.nz>
On Fri, Oct 13, 2006 at 09:33:14PM +1300, Nick Roberts wrote:
> If the global maintainers are agreeable, in principle, to it's inclusion after
> the next release, I will tidy it up and provide a ChangeLog. I would
> appreciate any clues as to where some things should go e.g waitpid in
> event-loop.c to linux-nat.c? (How?)
I'm agreeable in principle, though I don't have time to review it as
well as I'd like at the moment. Thank you for all your hard work on
this! I'll try hard to make the time.
I think you will need to add new target_ops methods; probably one to
set up async waiting and another to clean up afterwards. There
shouldn't be any reference to SIGCHLD directly in the common files (I'm
thinking about how to make this work on Windows, you see).
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-13 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 8:36 Nick Roberts
2006-10-13 13:11 ` Daniel Jacobowitz [this message]
2006-10-13 19:15 ` Nick Roberts
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=20061013131118.GA8144@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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