Comment 16 for bug 590651
Revision history for this message
| poy (poy) wrote Re: Applet crashes (visual c++ runtime library problem?) | #16 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
it could be worth a short trying to run a release mode build whose debugging symbols have not been stripped off (.exe around 100MB). then once a crash happens, select "Debug the program" in the Win crash dialog, fire up "gdb DCPlusPlus.exe", attach it to the application's PID (can be found via the Task Manager) with "attach <PID>", write "continue" in GDB, hit "No" on the crash dialog debugger selector which should reproduce the crash, then finally "bt full" in GDB.
(i guess these instructions could be generalized in an FAQ for people who don't want to keep running under GDB the whole time, but just want to attach to a crashed process later on.)
a custom build without the assertion should do too. though it is likely that by the time the assert gets hit, other things have already gone wrong...