From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH, RFC] Replace assert(0) with abort() or cpu_abort()
Date: Thu, 18 Mar 2010 05:19:25 -0400 (EDT) [thread overview]
Message-ID: <1850021959.400541268903965256.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <1317337484.400521268903946714.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
> The guest replacing one of QEMU's handlers with SIG_IGN or SIG_DFL would
> be "fun", too. No idea whether that's actually possible; I know next to
> nothing about user mode emulation.
No, the guest program cannot replace QEMU's handlers; the host OS always
sees host_signal_handler for all signals. But since host_signal_handler
is used also for SIGABRT, after all this is not so obscure...
Paolo
next parent reply other threads:[~2010-03-18 9:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1317337484.400521268903946714.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2010-03-18 9:19 ` Paolo Bonzini [this message]
2010-03-13 14:56 [Qemu-devel] [PATCH, RFC] Replace assert(0) with abort() or cpu_abort() Blue Swirl
2010-03-15 7:25 ` Markus Armbruster
2010-03-15 17:23 ` Blue Swirl
2010-03-15 18:19 ` [Qemu-devel] " Paolo Bonzini
2010-03-15 18:26 ` Blue Swirl
2010-03-15 18:33 ` Paolo Bonzini
2010-03-15 19:02 ` Blue Swirl
2010-03-15 18:28 ` Markus Armbruster
2010-03-15 18:36 ` [Qemu-devel] " Markus Armbruster
2010-03-16 8:24 ` [Qemu-devel] " Paolo Bonzini
2010-03-16 8:54 ` Markus Armbruster
2010-03-16 17:55 ` Jamie Lokier
2010-03-17 9:10 ` Paolo Bonzini
2010-03-17 19:50 ` Blue Swirl
2010-03-19 2:03 ` Jamie Lokier
2010-03-19 20:28 ` Blue Swirl
2010-03-18 8:36 ` Markus Armbruster
2010-03-16 17:52 ` Jamie Lokier
2010-03-16 18:35 ` Markus Armbruster
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=1850021959.400541268903965256.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.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).