JIT debugging - How to get the managed exception details?
- From: "Loy" <l.oyolox@xxxxxxxxx>
- Date: 27 Sep 2006 04:44:17 -0700
JIT debugging - How to get the managed exception details?
Problem: managed application is crashing on startup with unhandled
exception - need to understand the exception
I've set windbg to be my JIT debugger for managed code
HKLM\Software\Microsoft\.NetFramework\DbgJITDebugLaunchSetting =
(DWORD)2
HKLM\Software\Microsoft\.NetFramework\DbgManagedDebugger = (string)
c:\DebuggingTools\windbg.exe -p %ld
My test app throws new ApplicationException right from the main
WinDbg does attach to the process and break
So far - so good
Now I expect to be able to understand the exception type and location
!analyze -v is telling that the exception is 80000003 - break
instruction exception
Which is not what I expected - any idea why?
!sos.CurrenExceptionName is telling that: "This is not a managed
exception or not in KERNEL32!RaiseException"
How could I get the details of the ApplicationException?
Loy
.
- Follow-Ups:
- Re: JIT debugging - How to get the managed exception details?
- From: Oleg Starodumov
- Re: JIT debugging - How to get the managed exception details?
- Prev by Date: Re: Fusion binding - DEVPATH setting doesn't appear to work
- Next by Date: System.ExecutionEngineException
- Previous by thread: RE: Using BackgroundWorker in a browser's hosted user control
- Next by thread: Re: JIT debugging - How to get the managed exception details?
- Index(es):
Relevant Pages
|
Loading