views:

79

answers:

0

When I debug my program with netbeans using cygwin's g++, when it receives a sigabrt, I can't see my code anywhere in the call stack of any of the threads. Most of them are at ntdll!RtlEnableEaryCriticalSectionEventCreation() and one in RaiseException(). The problem is that after these there are only either some win32 functions without associated code or unresolved memory addresses in the stack, and not my code. If I run the same thing under linux with netbeans (and with the same project setup except for the necessary differences with paths) I see my code everywhere and the exception is a simple failed assert or my own stupidity reflected in an uninitialized pointer or something. Did I set up something wrong, or is this really as far as one can go with cygwin?