X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: "Krzysztof Duleba" <krzysan AT skrzynka DOT pl>
Subject:  Re: unable to debug code with std::string
Date:  Tue, 10 Jan 2006 19:27:07 +0100
Lines: 17
Message-ID: <dq0u9a$vfk$1@sea.gmane.org>
References:  <dq0lp6$o68$1 AT sea DOT gmane DOT org> <43C3DC3B DOT C10FFB1E AT dessent DOT net> <dq0omo$54u$1 AT sea DOT gmane DOT org> <43C3E9DC DOT 5C74D7DA AT dessent DOT net> <dq0ret$h3i$1 AT sea DOT gmane DOT org> <20060110180933 DOT GC29862 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version:  1.0
Content-Type:  text/plain; 	format=flowed; 	charset="ISO-8859-1"; 	reply-type=original
Content-Transfer-Encoding:  7bit
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

Christopher Faylor wrote:

>>tread.cc from 1.5.18 and from the cvs are very alike and both call
>>pthread_key::is_good_object in the same fashion. Why only 1.5.19 is 
>>having
>>this problem?
>
> Either it is because we are purposely trying to annoy you or it may be
> because cygwin 1.5.19 changed the way it detects invalid memory and gdb
> hasn't caught up to it.

What invalid memory? Do you suggest that std::string implementation in g++ 
is bogus? It might be true - there are no std::string related SIGSEGVs in 
gdb if I use g++ 2.95 or 3.3 instead of 3.4.

Krzysztof Duleba 




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