Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The VB6 debugger has a reputation for sometimes being a bit flaky, and I'm not sure it was ever supported on 64-bit operating systems. </p> <p>There are some other options for debugging VB6. </p> <ul> <li>You could try debugging the VB6 in the Visual C++ 6 debugger at the same time as the C++. Compile the VB6 into native code with symbols (create PDB files). Then you should be able to step from the C++ straight into the VB6 and still debug. I have done this before (not on 64-bit). Here's a Microsoft <a href="http://support.microsoft.com/kb/166275" rel="nofollow noreferrer">knowledgebase article</a> on doing this with C++ 5 - I think it's much the same in C++ 6. Here's <a href="https://stackoverflow.com/questions/1019071/how-to-use-vb6-debugger-on-outlook-property-page-ocx/1022019#1022019">info</a> on doing it with Visual C++ 2008 (!)</li> <li>Or you could try running the program in <a href="http://www.microsoft.com/whdc/devtools/debugging/default.mspx" rel="nofollow noreferrer">Windbg</a>, a free standalone debugger from Microsoft. Again compile your VB6 into native code with symbols (PDB files) and you will be able to debug your VB6 in Windbg. You should also be able to debug the C++ at the same time. <ul> <li>Here's a <a href="http://blogs.msdn.com/marklon/archive/2006/01/28/518616.aspx" rel="nofollow noreferrer">2006 blog post</a> by a Microsoft guy about using Windbg with VB6, and <a href="http://mtaulty.com/communityserver/blogs/mike_taultys_blog/archive/2004/08/03/4656.aspx" rel="nofollow noreferrer">2004 blog post</a> by another Microsoft VB guy with a brief introduction to Windbg. </li> </ul></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload