Re: unable to debug code with std::string
Krzysztof Duleba 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. There was a thread about this recently. pthread_key_create checks to see if the passed value happens to be already initialized, which in most cases is not true and thus faults - but it traps the fault which is why you don't normally see it. 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/
Re: unable to debug code with std::string
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/
Re: unable to debug code with std::string
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/
Re: unable to debug code with std::string
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: http://www.cygwin.com/ml/cygwin-xfree/2005-12/threads.html#00026 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/
Re: unable to debug code with std::string
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/
Re: unable to debug code with std::string
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/
