Debugging Visual Basic Code in a Visual C+= Debugger

********************UPDATE************* I've managed to make some progress on my own, so I'm changing the terms slightly. I'll accept a bid of $20 dollars to anyone who can successful show me how to install XP symbols for VC++ so I can see them in the stack trace. Thanks ***************ORIGINAL****************** I have an OCX control that was written in Visual Basic. Following the instructions in the following KB article: <[login to view URL]> 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. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). 4) Deliverable must accurately convey to user the information requested above. At the end of said aggreement, the buyer must fully understand how to map a given assembler statement to a corresponding statement in his VB application. * * *This broadcast message was sent to all bidders on Friday Jan 7, 2005 10:31:19 AM: Okay, I've managed to make some progress on my own, so I'm changing the terms slightly. I'll accept a bid of $20 dollars to anyone who can successful show me how to install XP symbols for VC++ so I can see them in the stack trace. Thanks ## Platform VB6, VC++ 6 Windows NT, 2000, XP