X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: "Krzysztof Duleba" Subject: Re: unable to debug code with std::string Date: Tue, 10 Jan 2006 18:38:54 +0100 Lines: 27 Message-ID: References: <43C3DC3B.C10FFB1E@dessent.net> <43C3E9DC.5C74D7DA@dessent.net> 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@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Brian Dessent >> 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. It does bother me. 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? This line surely has a purpose. What will break up if I comment it out? If nothing then why it is there? >> I must have missed it and I can't find it now. Any pointers? > > It was the thread starting here: > Thanks a lot. 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/