From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@redhat.com>
Subject: Re: Some more multi-fork fixes
Date: Sat, 25 Feb 2006 00:12:00 -0000 [thread overview]
Message-ID: <20060224230957.GA7834@nevyn.them.org> (raw)
In-Reply-To: <20060224224115.GA6792@nevyn.them.org>
On Fri, Feb 24, 2006 at 05:41:15PM -0500, Daniel Jacobowitz wrote:
> I'm up against a bit of a brick wall at the moment. I've got
> patches in my source tree to unify the single-threaded and
> multi-threaded code in the Linux native layer into a single
> combined target. But since this is an inherently single-threaded
> operation the multi-threaded code totally falls down - switching
> forks doesn't preserve things like the LWP list, leading to
> messy timeouts. I'm going to find some minimally painful
> way to make the two of them talk to each other.
FYI, I've got that more or less working now (as well as it was
previously). I'll post it in a bit.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-24 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 19:08 Daniel Jacobowitz
2006-01-27 20:04 ` Michael Snyder
2006-02-24 23:10 ` Daniel Jacobowitz
2006-02-25 0:12 ` Daniel Jacobowitz [this message]
2006-03-10 19:50 ` Michael Snyder
2006-03-10 19:54 ` Daniel Jacobowitz
2006-03-10 20:04 ` Michael Snyder
2006-03-01 22:15 ` 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=20060224230957.GA7834@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@redhat.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