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/
