Debugging Virtual Functions in Managed C++ App - TechRepublic
General discussion
October 19, 2005 at 08:52 AM
m_a_r_k

Debugging Virtual Functions in Managed C++ App

by m_a_r_k . Updated 20 years, 8 months ago

I am developing a Managed C++ application using Visual Studio.NET 2003. This is the first Managed C++ app I’ve ever written. While debugging, when I attempt to step into a virtual function, the debugger is unable to find the source file where the virtual function is located. I get this error:
“There is no source code available for the current location.” I can step into the assembly language of the called virtual function but not the C++ source code.

I also tried this with a very small test program consisting only of main(), one base class and one derived class containing a virtual function. The whole program was in a single module. I encountered the same debugger problem. The debugger couldn’t even locate the called source code even though it’s in the same module as the calling function. The code works and the debugger returns properly from the called function, but it just won’t show the source.

I rebuilt everything in unmanaged C++ and the debugger works fine. Very annoying not being able to debug virtual functions.

Anyone have a clue what’s going on? Thanks.

This discussion is locked

All Comments