On 11/10/2008 08:30 PM, Richard Hughes wrote:
Since it was probably pointers that created the problem in the first place, I doubt you want any more of them. </badpun>.
:-)
I've found that there are lots of little tricks needed to make mingw32 debugging possible. I'll try to list those that I think might be useful to you (in no particular order).
- gdb can attach to an already-running app. You can use either "gdb
--pid=1234" or run the "attach 1234" command in an existing gdb.
I tried that, but all I got was two empty calls and two calls to some windows stuff. I already messed a bit with the crash handler to no avail, but I will give DebugBreak() a try.
- If the crash is in Win32 code, you'll need Microsoft symbols to
backtrace out of Win32 and then gdb symbols to backtrace through Inkscape. This presents a problem, since gdb can't load Microsoft pdb files. What I do is attach gdb as the primary debugger and then windbg in noninvasive mode as the secondary. When gdb breaks in, start the stack trace in windbg to get the necessary parameters to continue it in gdb.
That sounds like fun ;-).
Thanks for educating me (and probably some others too?), I will have another try!
Diederik