tracking down error in MFC42.dll
- From: "Eric Margheim" <NOSPAM***eric@xxxxxxxxxxxxx***NOSPAM>
- Date: Fri, 25 Aug 2006 15:16:29 -0500
I have a bug in my ATL component code that is generating an Application
Error and COM+ error in the Event Viewer. I'm trying to pin down the source
code generating the error. The Application Error tells me it's in
MFC42.DLL and gives me a fault address. Can I use this to find out what
MFC call is blowing up?
I also have the call stack information in the COM+ error. I'm having
trouble making sense of it too.
Any thoughts on best course to track this down? I've put a bunch of
try/catch blocks in existing code in hopes to trap the next time it occurs.
It should send me an email if it catches anything but I'm not 100% confident
it will.
.
- Follow-Ups:
- Re: tracking down error in MFC42.dll
- From: Ajay Kalra
- Re: tracking down error in MFC42.dll
- Prev by Date: Re: Should Globally Needed Objects be Members in Main Frame, Application, or be Global?
- Next by Date: Re: Getting the ascii code from a char
- Previous by thread: Should Globally Needed Objects be Members in Main Frame, Application, or be Global?
- Next by thread: Re: tracking down error in MFC42.dll
- Index(es):
Relevant Pages
|
Loading