VS 2005 Debugger Very Slow With Multithreaded Applications

[Trecius]

Hello Newsgroupians:

I've recently switched from Visual Studio 2003 Standard to Visual Studio
2005 Standard, and I like some of the new features; however, the debugger is
driving me nuts.

Many of my applications are multithreaded, and when I use the debugger when
an application has spawned a second thread, the debugger becomes INCREDIBLY
slow; it takes a minute or two to "step over" or "step into." What is going
on? If the program is single threaded, or has not spawned the second thread,
then the debugger has a quick, normal response. As soon as it spawns the
thread, it becomes unbearably slow.

I never had this problem with Visual Studio 2003. I've noticed that this
problem is also not unique just to Visual C++; I've noticed that the debugger
is going slow in Visual C# as well if I spawn a new thread in my program.
Any ideas?

Thank you, all, for your help and consideration.


Trecius

[John Dallman]

Post by Trecius
Many of my applications are multithreaded, and when I use the
debugger when an application has spawned a second thread, the
debugger becomes INCREDIBLY slow; it takes a minute or two to "step
over" or "step into." What is going on? If the program is single
threaded, or has not spawned the second thread, then the debugger has
a quick, normal response. As soon as it spawns the thread, it
becomes unbearably slow.

It doesn't do that for me, with the multi-threaded programs I work on.
So likely there's something wrong with your installation, or there's
something about the way you do threading that VS.2005 doesn't like.

What sort of number of threads do you have running?

What APIs do you use for creating your threads?

How do you do your locking for data access?

[gilles]

With Visual Studio 2005 RTM there are several issues:

http://support.microsoft.com/kb/930776/en-us
When you debug, turn off the windows "watch auto", use the local window or
watch window

-Gilles

Post by John Dallman

Post by Trecius
Many of my applications are multithreaded, and when I use the
debugger when an application has spawned a second thread, the
debugger becomes INCREDIBLY slow; it takes a minute or two to "step
over" or "step into." What is going on? If the program is single
threaded, or has not spawned the second thread, then the debugger has
a quick, normal response. As soon as it spawns the thread, it
becomes unbearably slow.

It doesn't do that for me, with the multi-threaded programs I work on.
So likely there's something wrong with your installation, or there's
something about the way you do threading that VS.2005 doesn't like.
What sort of number of threads do you have running?
What APIs do you use for creating your threads?
How do you do your locking for data access?
--
"C++ - the FORTRAN of the early 21st century."