Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263246AbUDEVOM (ORCPT ); Mon, 5 Apr 2004 17:14:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263199AbUDEVOA (ORCPT ); Mon, 5 Apr 2004 17:14:00 -0400 Received: from mail.shareable.org ([81.29.64.88]:8600 "EHLO mail.shareable.org") by vger.kernel.org with ESMTP id S263228AbUDEVMv (ORCPT ); Mon, 5 Apr 2004 17:12:51 -0400 Date: Mon, 5 Apr 2004 22:12:36 +0100 From: Jamie Lokier To: "Richard B. Johnson" Cc: Chris Friesen , bero@arklinux.org, Linux kernel Subject: Re: Catching SIGSEGV with signal() in 2.6 Message-ID: <20040405211236.GD21649@mail.shareable.org> References: <20040405181707.GA21245@mail.shareable.org> <4071B093.9030601@nortelnetworks.com> <20040405204028.GA21649@mail.shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 847 Lines: 21 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 - 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/