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
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Subject: RE: pthreads "problem" Re: GDB always receives sigsegv with cygwin 1.3.13-2
Date: Wed, 16 Oct 2002 20:10:03 -0400
Message-ID: <83040F98B407E6428FEC18AC720F5D732DB731@exchange.tropicnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Rolf Campbell" <rcampbell AT tropicnetworks DOT com>
To: <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g9H0ACJ08265

> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com] 
> Sent: Wednesday, October 16, 2002 7:54 PM
>
> Ok.  This is occurring in code compiled via gcc 3.  gcc 3 
> uses a phreads mutex which is assigned to 
> PTHREAD_MUTEX_INITIALIZER.  There is a check for whether the 
> mutex pointer is valid or not.  It isn't valid as a pointer 
> but it is still a valid value.  So, a "harmless" SIGSEGV 
> occurs while checking the pointer.  The program traps the 
> SIGSEGV so you never see it but that is immaterial to gdb 
> which dutifully reports it.

So, silly question, why did this only start appearing in this new
version of cygwin?

> So, in the command line at least, you will be able to just 
> continue on.

Yeah, "cont" worked.  It worked in the gui too, I just couldn't figure
out how to click the button labeled "Continue".

-Rolf

--
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/