qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PATCH] linux-user: Proper exit code for uncaught signals
Date: Thu, 27 Nov 2008 12:16:15 +0000	[thread overview]
Message-ID: <20081127121615.GC18400@shareable.org> (raw)
In-Reply-To: <20081127114233.GC15592@networkno.de>

> > The proper exit code for dieing from an uncaught signal is -<signal>.
> > The kernel doesn't allow exit() or _exit() to pass a negative value.
> > To get the proper exit code we need to actually die from an uncaught
> > signal.

It's nothing like -<signal>, so the comment should be changed.

The general principle of sending yourself a signal to get the right
exit status is good.

> > +    sigfillset(&act.sa_mask);
> > +    act.sa_handler = SIG_DFL;
> > +    sigaction(host_sig, &act, NULL);

What if the SIG_DFL _host_ behaviour is not to terminate the host
process, but it has terminated the guest process?  Awkward one.



> > +    /* For some reason raise(host_sig) doesn't send the signal when
> > +     * statically linked on x86-64. */
> > +    kill(getpid(), host_sig);

Is getpid() always right here, and should tgkill() or tkill() be used when
clone is supported?

-- Jamie

  reply	other threads:[~2008-11-27 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 21:37 [Qemu-devel] [PATCH] linux-user: Proper exit code for uncaught signals Riku Voipio
2008-11-27 11:42 ` Thiemo Seufer
2008-11-27 12:16   ` Jamie Lokier [this message]
2008-11-27 12:44     ` Riku Voipio
2008-11-27 12:21   ` Riku Voipio

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=20081127121615.GC18400@shareable.org \
    --to=jamie@shareable.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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).