I've compiled and rebuilt the FlightGear application under a fresh installation of cygwin (I've been doing this for years, now) and when running flightgear I get a segfault at startup - something I've not seen before.
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 #1 0x6108dd7f in _sigfe () from /usr/bin/cygwin1.dll #2 0x59432d52 in ?? () #3 0x10022488 in ?? () #4 0x10022458 in ?? () #5 0x10022488 in ?? () #6 0x0022ed88 in ?? () #7 0x610af6b7 in pthread::once () from /usr/bin/cygwin1.dll #8 0x610af6b7 in pthread::once () from /usr/bin/cygwin1.dll #9 0x6108dd7f in _sigfe () from /usr/bin/cygwin1.dll #10 0x0022edb8 in ?? () #11 0x009aaa05 in _Unwind_SjLj_Register () #12 0x009aaa05 in _Unwind_SjLj_Register () #13 0x004011ad in main () I've checked with the mailing list and don't see a related question. Does the above trace suggest a problem with pthread implementation in cygwin, or does the first hint of trouble appear with the Unwind...() call? The "?" in line #10 in the "where" trace seems fishy, to me. Any suggestions on where to look next for help will be appreciated. Jon
cygcheck.out
Description: Binary data
-- 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/
