X-Spam-Check-By:	sourceware.org
Message-ID:	<44A53838.9070603@obbligato.org>
Date:	Fri, 30 Jun 2006 09:42:00 -0500
From:	David Greene <greened AT obbligato DOT org>
User-Agent:	Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	gdb: Segfault in pthread_mutex_init
X-Cray-VirusStatus:	clean
X-IsSubscribed:	yes
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

Apparently, the saga of pthreads and buggy gdb continues.

I've previously run into the famous gdb pthread_key_create
segfault on IRIX.  Apparently it exists on Cygwin as well.

But my program also segfaults in pthread_mutex_init:

Program received signal SIGSEGV, Segmentation fault.
0x610af064 in pthread_mutex::init () from /usr/bin/cygwin1.dll

Just like on IRIX, I can continue (many times for this
code, it turns out) and eventually get into a running state.

Is there a fix for this in some soon-to-be-released gdb?

                             -Dave

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