This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Debugging mixed gcc/MSVC programs


I am trying to debug an application with the following structure:  A .exe compiled using MSVC that performs LoadLibrary() calls on gcc-produced .dlls.  I want to set breakpoints and generally debug these DLLs.

The problem I am encountering is that it appears as though gdb is intercepting C++ exceptions issued by throw() statements in the MSVC-compiled code, even through these exceptions are caught and handled within the MSVC-compiled code.

The gdb debug session reports a SIGTRAP, and I am unable to continue from there.  I have tried handle SIGTRAP nostop (which seems like a bad idea) and also tried continuing and passing the trap on to the application.  It promptly segfaults.

Not knowing enough (or basically anything) about the gdb architecture, I am stuck.  Any help appreciated.

gcc --version yields 3.3.1 (cygming special)

gdb --version yields 2003-09-20-cvs (cygwin-special)

Cameron Stevens


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]