Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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:	Tue, 15 Oct 2002 19:41:16 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: GDB always receives sigsegv with cygwin 1.3.13-2
Message-ID:	<20021015234116.GB17874@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<83040F98B407E6428FEC18AC720F5D73E5005A AT exchange DOT tropicnetworks DOT com>
Mime-Version:	1.0
In-Reply-To:	<83040F98B407E6428FEC18AC720F5D73E5005A@exchange.tropicnetworks.com>
User-Agent:	Mutt/1.4i

On Tue, Oct 15, 2002 at 07:37:31PM -0400, Rolf Campbell wrote:
>I tried it with 2 different executables (both C++, both compiled with
>GCC3.2).  I tried it with both the stock gdb (20010428-3) & the one
>listed as experimental (20020718-1).  I also tried it with both 1.3.13-2
>& 1.3.12-4.
>
>The test was, set a breakpoint at the first line of main (done by
>default by the gui), and click the run button.  With both programs &
>both versions of GDB, the results were the same:  With 1.3.12-4, it
>worked fine.  With 1.3.13-2, gdb got the sigsegv signal.

You can ask Robert Collins about this.  This is in pthreads code.  There
is some pointer validation going on that causes this.  There are two of
these, in fact.  I meant to mention them in cygwin-developers but I
forgot.

Just continue beyond the SIGSEGV and you should be ok.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -