On Fri, 2006-02-10 at 21:31 -0800, Brian Dessent wrote: > skaller wrote: > > > Program received signal SIGSEGV, Segmentation fault. > > 0x610ae938 in pthread_key_create () from /usr/bin/cygwin1.dll > > (gdb) bt > > *sigh* Not an actual fault.
Ah, ok. Thanks. But now it is worse! I type continue and the program aborts with a core dump. The statically linked version doesn't. The code IS different: the cygwin dynamic link version is the same as the linux code (which works). There is one difference though: on Linux I'm using gcc 4.0, Cygwin is using gcc 3.4.4. Curious -- seems like the dll isn't loaded until it is referenced, is that right? (Thats bad .. is there any way to force all the symbols to resolve at startup?) -- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net -- 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/
