From: "Michael S. Zick" <mszick@morethan.org>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: gsyprf11 and 2.6.13-rc3-pa1
Date: Tue, 16 Aug 2005 10:06:50 -0500 [thread overview]
Message-ID: <200508161006.50880.mszick@morethan.org> (raw)
In-Reply-To: <4301F979.2050709@tausq.org>
On Tue August 16 2005 09:34, Randolph Chung wrote:
> > See http://www.opengroup.org/onlinepubs/009695399/functions/signal.html.
> >
> > This is implementation defined.
>
> I remember reading that, but does that mean hanging the system is ok? :-)
>
The answer seems spread across several paragraphs...
If you get a signal while handling a signal, you can do a SIGDFL OR
block handling the new signal until the original signal is handled.
That applies to SIGSEGV also.
The paragraph listing SIGSEGV as a special case is preceded by:
"If and when the function returns..."
So, by my reading, if the SIGSEGV handler never returned -
then looping in the SIGSEGV handler could not happen.
Translation: Seems to be a design choice, if hanging the system
is considered to be the meaning of: "behavior is undefined"
which is reached if the SIGSEGV handler does return.
Mike
> randolph
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
>
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-08-16 15:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 9:17 [parisc-linux] Re: gsyprf11 and 2.6.13-rc3-pa1 Joel Soete
2005-08-16 10:10 ` Randolph Chung
2005-08-16 13:39 ` John David Anglin
2005-08-16 14:34 ` Randolph Chung
2005-08-16 15:06 ` Michael S. Zick [this message]
2005-08-16 23:57 ` Randolph Chung
2005-08-17 0:08 ` John David Anglin
2005-08-17 0:50 ` John David Anglin
[not found] <no.id>
2005-08-16 3:32 ` John David Anglin
[not found] <20050812180551.GA32609@colo.lackof.org>
2005-08-13 0:00 ` John David Anglin
2005-08-13 5:02 ` Grant Grundler
2005-08-13 5:11 ` John David Anglin
2005-08-13 5:14 ` John David Anglin
2005-08-13 13:40 ` James Bottomley
2005-08-13 17:46 ` John David Anglin
2005-08-13 19:30 ` John David Anglin
2005-08-16 3:02 ` Randolph Chung
2005-08-16 3:18 ` John David Anglin
2005-08-14 1:32 ` John David Anglin
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=200508161006.50880.mszick@morethan.org \
--to=mszick@morethan.org \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.