"Jon S. Berndt" wrote: > When running under gdb, this is the message I get: > > Program received signal SIGSEGV, Segmentation fault. > 0x610ae938 in pthread_key_create () from /usr/bin/cygwin1.dll > > Typing "where" in gdb gives this trace: > > (gdb) where > #0 0x610ae938 in pthread_key_create () from /usr/bin/cygwin1.dll
What you are seeing: - does not represent an actual problem in the pthread library - is not an actual segfault - is a bug/misfeature in gdb that has been fixed in CVS - can be worked around just by typing "c" or "continue" - has been discussed in depth, at length, ad infinitum, over and over and over on this list numerous times in the past, so please read those threads. Try a google search for: site:cygwin.com inurl:ml inurl:cygwin inurl:2006 gdb sigsegv 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/
