From: "Andreas Färber" <afaerber@suse.de>
To: Alex Barcelo <abarcelo@ac.upc.edu>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] Signal management in qemu-user
Date: Thu, 24 May 2012 00:50:06 +0200 [thread overview]
Message-ID: <4FBD699E.8000403@suse.de> (raw)
In-Reply-To: <CAFKAgTcTtsKUVwcqB=+1Mfq+Xz+1Spc440tcBYtdYk=YfVzHUg@mail.gmail.com>
Am 24.05.2012 00:38, schrieb Alex Barcelo:
>>> Running it in a i386 machine works and gives an output of "0x0d\n0x20".
>>> Running it in a qemu-i386 segfaults. Because the self-modifying code
>>> raises a SIGSEGV in the qemu (I understand that it is the method used by
>>> qemu to handle self-modifying code). But the sigprocmask disables the
>>> SIGSEGV and the qemu-user... does nothing to avoid it. So the SIGSEGV is
>>> unmanaged and breaks the program.
>>
>> Alex has the following SIGSEGV workaround queued for our openSUSE package:
>> http://repo.or.cz/w/qemu/agraf.git/commit/0760e24b52ff20a328f168ed23b52c9b9c0fd28f
>>
>> Don't know if it fixes your specific problem. Peter had some ideas how
>> to refactor signal handling but iirc didn't have time to work on it himself.
>
> Is it similar at all?
Peter answered that already: No, it isn't. Sorry for the confusion.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-05-23 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 9:23 [Qemu-devel] Signal management in qemu-user Alex Barcelo
2012-05-17 13:33 ` Andreas Färber
2012-05-17 13:42 ` Peter Maydell
2012-05-17 14:16 ` Andreas Färber
2012-05-23 22:38 ` Alex Barcelo
2012-05-23 22:50 ` Andreas Färber [this message]
2012-05-23 23:04 ` Peter Maydell
2012-05-24 7:19 ` Alex Barcelo
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=4FBD699E.8000403@suse.de \
--to=afaerber@suse.de \
--cc=abarcelo@ac.upc.edu \
--cc=agraf@suse.de \
--cc=peter.maydell@linaro.org \
--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).