The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Catching SIGSEGV with signal() in 2.6
Date: Mon, 05 Apr 2004 19:04:15 -0700	[thread overview]
Message-ID: <4072101F.3010603@redhat.com> (raw)
In-Reply-To: <200404052040.54301.kevin.hendricks@sympatico.ca>

Kevin B. Hendricks wrote:

> For some reason, the segfault generated by trying to write to address 0 can 
> not be properly caught anymore (or at least it appears that way to me).

If the code would be correct you'd see the expected behavior.

> void SignalHdl( int sig )
> {
>   bSignal = 1;
>   longjmp( check_env, sig );
> }

Since you jump out of a signal handling you must use siglongmp


> int check( TestFunc func, void* p )
> {
>   int result;
>   bSignal = 0;
>   if ( !setjmp( check_env ) )

And sigsetjmp(check_env, 1) here.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖

  reply	other threads:[~2004-04-06  2:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06  0:40 Catching SIGSEGV with signal() in 2.6 Kevin B. Hendricks
2004-04-06  2:04 ` Ulrich Drepper [this message]
2004-04-06  3:01   ` Kevin B. Hendricks
2004-04-06  4:08     ` Ulrich Drepper
2004-04-06 12:02       ` Kevin B. Hendricks
2004-04-06 15:53       ` Edgar Toernig
  -- strict thread matches above, loose matches on Subject: below --
2004-04-05 15:25 bero
2004-04-05 18:17 ` Jamie Lokier
2004-04-05 19:16   ` Chris Friesen
2004-04-05 20:40     ` Jamie Lokier
2004-04-05 20:59       ` Richard B. Johnson
2004-04-05 21:11         ` Chris Friesen
2004-04-05 21:12         ` Jamie Lokier
2004-04-05 21:23   ` bero

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=4072101F.3010603@redhat.com \
    --to=drepper@redhat.com \
    --cc=kevin.hendricks@sympatico.ca \
    --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