» An ultimate catalog of computer data
Forum posts for drwtsn32.exe
Post-mortem .Net debugging
Added a .Net component (C#, COM interop) to an old VB6 application. The old application crashes sometimes (access violation), before and after the change. The difference however is that the post-mortem debugger (i.e. drwtsn32.exe) is not started anymore.
Catching the error in C# is not an option as the bug is not part of the .Net call stack, so MyHandler is not triggered either:
AppDomain currentDomain = AppDomain.CurrentDomain;
currentDomain.UnhandledException += new UnhandledExceptionEventHandler(MyHandler);
How to trigger post-mortem debugging again?
Thanks in advance for any help! GMore
View complete forum thread with replies
Other posts related to drwtsn32.exe
See Related Forum Messages: Follow the Links Below to View Complete Thread
Drtsn32.exe only catching exception once per reboot
Post-mortem .Net debugging
How to debug a disappearing app
Enabling jitDebugging for WinForms
Win32: Is there a difference between Dr. Watson's full/mini dumps and writing my own?