major trouble debugging C# and C++ together

  • Thread starter Thread starter Christophe Marcel
  • Start date Start date
C

Christophe Marcel

Hi,

My application is a C# Windows Forms client that uses a C++ COM server (a
dll). When I opt to debug both C# and C++ code at the same time, the
debugging environment becomes extremely slow and unstable.

I have noticed that the more expressions are in the watch list, the slower
it takes for the environment to single step through C++ code (and I am only
talking about having 5 simple pointers / expressions in the list). Things
sometimes get very unstable, where the entire windows environment takes 30
seconds to process any mouse click / keystroke. It takes for ever to bring
up Task Manager to kill the application (even though Task Manager doesn't
even report high CPU utilization by the process, and music keeps playing
without interruption...)

Is this kind of behavior typical when debugging both CLR and C++ compiled
code simultaneously?

Thanks mucho,

Christophe
http://cmarcel.net
 
Christophe said:
Hi,

My application is a C# Windows Forms client that uses a C++ COM server (a
dll). When I opt to debug both C# and C++ code at the same time, the
debugging environment becomes extremely slow and unstable.

I have noticed that the more expressions are in the watch list, the slower
it takes for the environment to single step through C++ code (and I am only
talking about having 5 simple pointers / expressions in the list). Things
sometimes get very unstable, where the entire windows environment takes 30
seconds to process any mouse click / keystroke. It takes for ever to bring
up Task Manager to kill the application (even though Task Manager doesn't
even report high CPU utilization by the process, and music keeps playing
without interruption...)

Is this kind of behavior typical when debugging both CLR and C++ compiled
code simultaneously?
Click to expand...

Yes, completely expected for a 13th rev. of a major product.

Take a look at your per-process VM size in the Task Manager (you may have to
display the VM Size column) -- devenv.exe is probably hogging most/all of
available memory and things grind to a halt.

"Take 2 memory chips and call me in the morning."
 
Back
Top