From: Jamie Lokier <jamie@shareable.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] linux-user NPTL problem with signals
Date: Sun, 27 Sep 2009 15:13:12 +0100 [thread overview]
Message-ID: <20090927141312.GB28368@shareable.org> (raw)
In-Reply-To: <4ABB87A9.9060706@mlbassoc.com>
Gary Thomas wrote:
> On 09/23/2009 03:51 PM, Gary Thomas wrote:
> >I'm running a multi-threaded program (linux-user on i386). I
> >have a problem with signals; when one arrives, the running
> >thread abruptly changes :-(
> >
> >Anyone have any ideas about this?
> >
>
> I've tracked this down to the fact that there should be a
> unique value for the GS segment register (at least) per thread.
> This doesn't seem to be the case and when a signal is dispatched,
> the GS segment register is updated with [probably] the most recent
> value created by a new thread, not the running thread.
Nasty. NPTL is not the only software which depends on the segment
registers keeping their correct values. Wine, DOSemu among others
depend on all the segment registers.
-- Jamie
prev parent reply other threads:[~2009-09-27 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 21:51 [Qemu-devel] linux-user NPTL problem with signals Gary Thomas
2009-09-24 14:52 ` Gary Thomas
2009-09-27 14:13 ` Jamie Lokier [this message]
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=20090927141312.GB28368@shareable.org \
--to=jamie@shareable.org \
--cc=gary@mlbassoc.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).