From: Sriranga Veeraraghavan <ranga@CSUA.Berkeley.EDU>
To: "Peter M. Jansson" <petej@clickvision.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: SIGALRM can't be delivered after longjmp from handler?
Date: Wed, 15 Mar 2000 17:47:22 -0800 [thread overview]
Message-ID: <200003160147.RAA04377@soda.csua.Berkeley.edu> (raw)
In-Reply-To: Your message of "Wed, 15 Mar 2000 13:41:29 EST." <38CFD959.52E9F85@clickvision.com>
For other signals like SEGV and BUS and INTR, I had to re-enable the
signal by calling signal() after longjmp as specified in the signal(2)
manpage for Linux:
"Unlike on BSD systems, signals under Linux are reset to their default
behavior when raised. However, if you include <bsd/signal.h> instead
of <signal.h> then signal is redefined as __bsd_signal and signal has
the BSD semantics. Both versions of signal are library routines built
on top of sigaction(2)."
I changed your example program to restore the signal handler routine
once the signal is raised and it worked as you described. I did not
try using <bsd/signal.h>. You may wish to try that. I prefer just
restoring the signal handler, since this avoid #ifdefs for different
platorms.
----ranga <ranga@soda.berkeley.edu>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-16 1:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 18:41 SIGALRM can't be delivered after longjmp from handler? Peter M. Jansson
2000-03-16 1:47 ` Sriranga Veeraraghavan [this message]
2000-03-16 1:50 ` Peter M. Jansson
2000-03-16 1:57 ` David A. Gatwood
2000-03-16 1:55 ` Peter M. Jansson
2000-03-16 2:10 ` David A. Gatwood
2000-03-16 2:07 ` Peter M. Jansson
2000-03-16 2:25 ` David A. Gatwood
2000-03-16 2:18 ` Peter M. Jansson
-- strict thread matches above, loose matches on Subject: below --
2000-03-16 9:35 D.J. Barrow
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=200003160147.RAA04377@soda.csua.Berkeley.edu \
--to=ranga@csua.berkeley.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=petej@clickvision.com \
/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).