Tracing

I have a VB control that is calling into a VC DLL and I need to debug the
interaction between the two of them. I can start VB, start the program and
attach VC to VB and it breaks in the VC DLL with no problem. At the same
time, VB can tract through its own code in the normal fashion. A couple of
days ago for no reason that I can think of, I could see back into the VB
call stack and even trace through the VB code from within VC. This was
*great* but I have not been able to duplicate that set up again. Was I
delusional or is there some way to set things up so that VC can see into the
VB stack?
--
Richard Lewis Haggard
www.Haggard-And-Associates.com


.

Relevant Pages

  • Re: How to debug load-time DLL exception?
    ... It is safe to call other functions in Kernel32.dll, ... Calling imported functions other than those located in Kernel32.dll may ... User, Shell, and COM functions can cause access violation errors, because ... here is the better stack trace:> ...
    (microsoft.public.win32.programmer.kernel)
  • Re: tracking down error in MFC42.dll
    ... The beginning of the call stack resolves to the following: ... Run an application that uses mfc42.dll under debugger, ... The same could be done for your dll if it would be built with debug information ... If you put symbols of your dll on the target system, ...
    (microsoft.public.vc.mfc)
  • Re: STA cannot prevent multiple client calls accessing at the same time??
    ... making a cross-apartment call from an STA. ... DLL object runs on. ... As for the suddenly changing call stack - that's a debugger quirk - ... And maybe I am not an Appz ...
    (microsoft.public.vc.atl)
  • Re: AD+ crash logs and .dmps Part II
    ... This a .dll provided by an online payment verification ... The Debugger docs have some basic info but overall, understanding ... details the formation and usage of the stack. ...
    (microsoft.public.inetserver.iis.security)
  • 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)