Re: Tracing

Ah! VC is allowing me to trace through VB code again. The situation was a
Grams program that was using a VB OCX that called into a VC DLL. I started a
VC IDE, attached to Grams and was able to set break points in both the C++
and VB code. However, when I do the same thing to hosting a test program
that hosts the VB OX, I do not get to see the VB code. Any ideas why this
might be?
--
Richard Lewis Haggard
www.Haggard-And-Associates.com
"Richard Lewis Haggard" <HaggardAtWorldDotStdDotCom> wrote in message
news:e$OiNUIcGHA.1260@xxxxxxxxxxxxxxxxxxxxxxx
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