qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Handle terminating signals.
Date: Tue, 12 Aug 2008 12:46:06 +0100	[thread overview]
Message-ID: <48A177FE.6070909@eu.citrix.com> (raw)
In-Reply-To: <18593.24673.304649.806330@mariner.uk.xensource.com>

Ian Jackson wrote:

> Gerd Hoffmann writes ("Re: [Qemu-devel] [PATCH] Handle terminating signals."):
>> Ian Jackson wrote:
>>> SIGQUIT should not be in this list.  QUIT does not mean `please
>>> terminate'.  It's a signal used for debugging purposes and usually
>>> means `please pretend this program took a SEGV'.  The default action
>>> is to die and dump core, and this should be preserved.
>> Ok, we could take the SIGSEGV cleanup route, then call abort().  That
>> should come close enougth.  Does that sound ok?
> 
> No, because the program should not attempt to catch SEGV either.
> 

I agree.
The idea of trying a clean exit when a termination signal is received is
good, but do we really need the complicated fatalsig_call_handlers and
fatalsig_register_handler system?

  reply	other threads:[~2008-08-12 11:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 11:48 [Qemu-devel] [PATCH] Handle terminating signals Gerd Hoffmann
2008-08-11 16:52 ` Ian Jackson
2008-08-11 19:46   ` Gerd Hoffmann
2008-08-12 10:05     ` Ian Jackson
2008-08-12 11:46       ` Stefano Stabellini [this message]
2008-08-12 18:29       ` Gerd Hoffmann
2008-08-12 19:29         ` M. Warner Losh
2008-08-12 19:42           ` Gerd Hoffmann
2008-08-12 19:49             ` Anthony Liguori
2008-08-13  8:27             ` Daniel P. Berrange
2008-08-13 13:29         ` Ian Jackson

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=48A177FE.6070909@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.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).