public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: daw@taverner.cs.berkeley.edu (David Wagner)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.x signal handler bug
Date: Sat, 26 Jun 2004 01:33:18 +0000 (UTC)	[thread overview]
Message-ID: <cbijou$nfa$1@abraham.cs.berkeley.edu> (raw)
In-Reply-To: 40DCBBC3.2010308@di.uoa.gr

Neither printf() nor longjmp() are safe to call from within
the sighandler.  Have you tried deleting printf() and replacing
longjmp() with siglongjmp()?  This is a FAQ; search the list archives
for details.

  parent reply	other threads:[~2004-06-26  1:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-25 23:56 2.6.x signal handler bug Paul Maurides
2004-06-26  0:07 ` Andrew Morton
2004-06-26  1:33 ` David Wagner [this message]
2004-06-28 21:56 ` Jörn Engel
  -- strict thread matches above, loose matches on Subject: below --
2004-06-26 14:33 Steve G
2004-06-26 16:05 ` Davide Libenzi
2004-06-27 22:16   ` Andries Brouwer
2004-06-27 22:45     ` Davide Libenzi
2004-06-27 22:51       ` Davide Libenzi
2004-06-28  2:01         ` Steve G
2004-06-28 11:26         ` Steve G
2004-06-28 14:56           ` Davide Libenzi

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='cbijou$nfa$1@abraham.cs.berkeley.edu' \
    --to=daw@taverner.cs.berkeley.edu \
    --cc=daw-usenet@taverner.cs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.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