All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
	bero@arklinux.org, Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Catching SIGSEGV with signal() in 2.6
Date: Mon, 5 Apr 2004 22:12:36 +0100	[thread overview]
Message-ID: <20040405211236.GD21649@mail.shareable.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0404051644440.2948@chaos>

Richard B. Johnson wrote:
> Are you using a longjump to get out of the signal handler?
> You may find that you can trap SIGSEGV, but you can't exit
> from it because it will return to the instruction that
> caused the trap!!!

Thanks for stating the obvious! :)

No, actually I'm changing memory protection with mprotect() inside the
handler, so when it returns the program can continue.

But that's not relevant to the OpenOffice problem.  They have a
program which traps SIGSEGV with 2.4 and terminates suddenly with 2.6.
Obviously they aren't just returning else it wouldn't work with 2.4.

-- Jamie

  parent reply	other threads:[~2004-04-05 21:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 15:25 Catching SIGSEGV with signal() in 2.6 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 [this message]
2004-04-05 21:23   ` bero
  -- strict thread matches above, loose matches on Subject: below --
2004-04-06  0:40 Kevin B. Hendricks
2004-04-06  2:04 ` Ulrich Drepper
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

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=20040405211236.GD21649@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=bero@arklinux.org \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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 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.