X-Spam-Check-By: sourceware.org
Message-ID: <43C3DC3B.C10FFB1E@dessent.net>
Date: Tue, 10 Jan 2006 08:09:31 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: unable to debug code with std::string
References: <dq0lp6$o68$1 AT sea DOT gmane DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

Krzysztof Duleba wrote:

> Program received signal SIGSEGV, Segmentation fault.
> 0x610aea58 in pthread_key_create () from /usr/bin/cygwin1.dll
> 
> This is a regression from 1.5.18.

That's normal.  You can just continue.  There was a thread about this
recently.  pthread_key_create checks to see if the passed value happens
to be already initialized, which in most cases is not true and thus
faults - but it traps the fault which is why you don't normally see it.

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/