Re: tracking down error in MFC42.dll

It appears to be in release build only. Can you not reproduce it in
debug build. It will belp as you will have the stack to look at.

---
Ajay

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.

.

Relevant Pages

  • Re: Need Help Debugging
    ... you should use straight and plain ADPlus.VBS from the debugger package. ... debug info loaded, etc... ... does that avoid using the stack ?!? ... which is our custom CRITICAL_SECTION class. ...
    (microsoft.public.win32.programmer.kernel)
  • [PATCH] i386: get rid of the use of KPROBE_ENTRY / KPROBE_END
    ... * Debug traps and NMI can happen at the one SYSENTER instruction ... * that sets up the real kernel stack. ... * a debug fault, and the debug fault hasn't yet been able to ...
    (Linux-Kernel)
  • Re: Ecos, LwIP, PPP and GPRS
    ... the modem has an IP stack built in. ... FTP is the most important right now. ... >>while printing the messages over another serial port. ... >Can you modify the debug output to go to a memory buffer instead of the ...
    (comp.arch.embedded)
  • Re: Problem only in release version!
    ... Debug version may still have the problem, but the stack space is better ... memory or a buffer on the stack is not always caught. ... > Just to affirm Jochen's point, the Debug version initializes most ...
    (microsoft.public.dotnet.languages.vc)
  • Re: tracking down error in MFC42.dll
    ... (I used WinDbg to do that, but the same can be done ... The same could be done for your dll if it would be built with debug ... If you put symbols of your dll on the target system (in the same ... what the call stack shows. ...
    (microsoft.public.vc.mfc)
Loading