X-Spam-Check-By: sourceware.org
Message-ID: <43C3E9DC.5C74D7DA@dessent.net>
Date: Tue, 10 Jan 2006 09:07:40 -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> <43C3DC3B DOT C10FFB1E AT dessent DOT net> <dq0omo$54u$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:

> Thanks. I don't like the idea of seeing this message anytime I debug code
> that's using std::string, though, and I don't think it's "normal".

If it bothers you, comment out the "if (pthread_key::is_good_object
(key))" check in thread.cc.  I'm not sure if it's possible for the app
to check at runtime if it's being debugged but if so that might be a
better way to handle it.  Either that or add some code to gdb to make it
possible to silently passthru SIGSEGVs generated/handled interally by
this "myfault" infrastructure.

> > There was a thread about this recently.
> 
> I must have missed it and I can't find it now. Any pointers?

It was the thread starting here:
<http://www.cygwin.com/ml/cygwin-xfree/2005-12/threads.html#00026>

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/