I have an OCX control that was written in Visual Basic. Following the
instructions in the following KB article:

http://support.microsoft.com/kb/166275/EN-US/

I was able to run my component inside and EXE and monitor it in the
Visual C++ debugger. Which is great because you can see any exceptions
that occur under the hood that VB ignores and really get a chance to
optimize things.

However, I've found a problem and I need some help. There is one point
in my code that generates dozens and dozens of floating point
exceptions. These are uncaught by VB, but I'm sure they are slowing
down my code. The problem I'm facing is that when I set the C++
debugger to break on these exceptions, it always breaks somewhere in
an assembly void. :(

Is there a way to "step out" of this assembler or to map the address
somehow so I can easily get the last VB statement executed? I'm able
to easily set a breakpoint on a VB statement and then walk through the
assembler.....is there a way to reverse this process?

Please help....Very critical I lock down these and other errors that
occuring in the code.

Hi,
  If you could send your details through this. I could check,
afterwards i will reply.

Regards,
Indian.

I'm not sure I understand what you're looking for.