X-Spam-Check-By:	sourceware.org
Message-ID:	<4497E364.19EACCFB@dessent.net>
Date:	Tue, 20 Jun 2006 05:00:36 -0700
From:	Brian Dessent <brian AT dessent DOT net>
X-Mailer:	Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Thread-related segfault with cygwin 1.5.19-4
References:	<GGEHLLAOPBJBGJGBDADHOEBEDJAA DOT jsb AT hal-pc DOT org>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
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

"Jon S. Berndt" wrote:

> When running under gdb, this is the message I get:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x610ae938 in pthread_key_create () from /usr/bin/cygwin1.dll
> 
> Typing "where" in gdb gives this trace:
> 
> (gdb) where
> #0  0x610ae938 in pthread_key_create () from /usr/bin/cygwin1.dll

What you are seeing:

- does not represent an actual problem in the pthread library
- is not an actual segfault
- is a bug/misfeature in gdb that has been fixed in CVS
- can be worked around just by typing "c" or "continue"
- has been discussed in depth, at length, ad infinitum, over and over
and over on this list numerous times in the past, so please read those
threads.  Try a google search for: site:cygwin.com inurl:ml inurl:cygwin
inurl:2006 gdb sigsegv

Brian

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