Re: Capture unhandled exception
From: Michael J. Salamone [eMVP] (mikesa#at#entrek#dot#com)
Date: 04/29/04
- Next message: Paul Cameron: "Re: Help with pOEMCalcFSPages"
- Previous message: David Jones: "RE: USB Host to Host connection WCE<->PC"
- In reply to: Rodger Higgins: "Re: Capture unhandled exception"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 29 Apr 2004 06:13:52 -0700
That's right.
You can write a JIT debugger that gets registered with the system. When a
second chance exception occurs, it gets invoked with the process id of the
process that caused the exception.
This works fine for CE 4.0 and higher I believe. CE 3.0 and earlier worked
sort of - the JIT debugger was invoked on *first* chance exceptions, so
wasn't a very practical solution.
-- Michael Salamone [eMVP] Entrek Software, Inc. www.entrek.com "Rodger Higgins" <rhiggins@earthling.net> wrote in message news:%23Y5HjjeLEHA.3712@TK2MSFTNGP10.phx.gbl... > Sorry, probably should have gave more information. I would like to > implement a system wide monitor that captures any unhandled exceptions > and performs error recovery. This would need to capture exceptions > irregardless of where they occurred. My assumption was the > __try/__except only work in the context of a particular program, correct? > > Michael J. Salamone [eMVP] wrote: > > > __try/__except? Or, a debugger program (either PB IDE debugger or roll your > > own). Of course, either method can actually handle the exception, making it > > not unhandled ;)
- Next message: Paul Cameron: "Re: Help with pOEMCalcFSPages"
- Previous message: David Jones: "RE: USB Host to Host connection WCE<->PC"
- In reply to: Rodger Higgins: "Re: Capture unhandled exception"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|