"Jon S. Berndt" wrote:
> via various google searches, and asking other developers for help. I
> searched the cygwin mailing list archives, and checked the cygwin FAQ
> ("Known problems ..."). Even though this is not a real cygwin problem, if
> this question gets asked so often, it might be worth a
> 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 a
"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
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 SI
4 matches
Mail list logo
