Kai Tietz <[email protected]> writes: > for sure there are some issues in gdb about debugging pe and pe+ coff > executables in some scenarios. For pe+ ones the backtrace shown by > gdb is much more reliable then for the 32-bit case, as pe+ makes use > of the function-tables, which helps on unwinding pretty much. > Nevertheless there are some issues when call-stack gets corrupted, or > - as here shown - jump to 0x0 address happens. As for both cases the > unwinding doesn't work anymore correct.
Right. If the stack is messed, there is no debugger that can show a reliable trace. I've seen that on Visual Studio lots of times. If the problem is gdb, you can try an alternative method for getting an stack trace. drmingw, for instance, which is available on the MSYS2 repo. ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
