X-Spam-Check-By: sourceware.org Date: Tue, 10 Jan 2006 13:09:33 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: unable to debug code with std::string Message-ID: <20060110180933.GC29862@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <43C3DC3B.C10FFB1E@dessent.net> <43C3E9DC.5C74D7DA@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Tue, Jan 10, 2006 at 06:38:54PM +0100, Krzysztof Duleba wrote: >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? 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. As Brian said: http://cygwin.com/acronyms/#PTC . >This line surely has a purpose. What will break up if I comment it >out? If nothing then why it is there? I wouldn't recommend commenting it out, actually. cgf -- 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/