X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: "Krzysztof Duleba" Subject: Re: unable to debug code with std::string Date: Tue, 10 Jan 2006 17:51:53 +0100 Lines: 18 Message-ID: References: <43C3DC3B DOT C10FFB1E AT dessent DOT 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 AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Brian Dessent 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. 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". > There was a thread about this recently. I must have missed it and I can't find it now. Any pointers? 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/