From: "Clifford T. Matthews" <ctm@ardi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17043.39755.573568.293067@newbie.ardi.com>
Date: Tue, 24 May 2005 15:23:23 -0600
To: Chris Wright <chrisw@osdl.org>
Cc: "Clifford T. Matthews" <ctm@ardi.com>, linux-kernel@vger.kernel.org
Subject: Re: trouble trapping SEGV on 2.6.11.2 & 2.6.12-rc4
In-Reply-To: <20050524204310.GJ23013@shell0.pdx.osdl.net>
References: <17043.36668.164277.860295@newbie.ardi.com>
	<20050524204310.GJ23013@shell0.pdx.osdl.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1103
Lines: 27

>>>>> "Chris" == Chris Wright <chrisw@osdl.org> writes:

    Chris> 2.6 has been fixed...  So your program (which happens to be
    Chris> slightly buggy) no longer works as you expected.  See
    Chris> below.

Thanks for the quick response.  Using sigsetjmp and siglongjmp makes
the program print two lines.

I read the setjmp / sigsetjmp documentation and misunderstood it.

I had already seen that if I inserted "signal (SIGSEGV, segv_handler)"
before the second setjmp (not sigsetjmp), the program (under 2.6
kernels) still would die.

I guess what happens there is that after coming back from the longjmp,
the error handler is still segv_handler, but the receipt of the SEGV
signal itself is blocked and if you take a SEGV when the receipt of
SEGV is blocked a program dies with a SEGV, even if you have a SEGV
handler.

--Cliff Matthews <ctm@ardi.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/