Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Fri, 22 Oct 2004 11:15:13 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Is there a fix for IsBadWritePtr Segfault?
Message-ID:	<20041022151513.GD5622@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<417878AC DOT 6070004 AT bluepeach DOT com> <20041022043622 DOT GB31220 AT trixie DOT casa DOT cgf DOT cx> <41790F38 DOT 1070901 AT bluepeach DOT com>
Mime-Version:	1.0
In-Reply-To:	<41790F38.1070901@bluepeach.com>
User-Agent:	Mutt/1.4.1i

On Fri, Oct 22, 2004 at 09:46:32AM -0400, Richard Schmitt wrote:
>Well, I did find a post in the cygwin-xfree mailing list that had a 
>patch for gdb.  I applied the patch and it works well.  If anyone knows 
>of a better approach, please post it.
>
>http://www.cygwin.com/ml/cygwin-xfree/2004-10/msg00158/segv.diff

Well, that is at least a starting point or you could just use the
command that Kensuke mentioend:

handle SIGSEGV nostop noprint

Now, in the spirit of free software, a non-hacky patch submitted to the
right place (the gdb-patches mailing list at sourceware.org) would probably
get the problem fixed.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -