Geek Answers Handbook

Suggestions for debugging a multi-threaded application

I have problems stepping through debugging a multi-threaded .NET application in Visual Studio 2008.

With each step line, Visual Studio gets slower and slower (it takes more time to go to the next line) and usually freezes after a few lines (I get the prompt “Visual Studio busy”), and I need to stop debugging.

I suspect the problem is that the application has several TCP / IP clients connected, which means that every time I make a breakpoint, their network buffer is full until I continue my application. Whenever I use F10to go to the next line of code, Visual Studio will soon wake up all the other threads to process the input.

Does anyone have experience with such problems and suggestions on how to avoid them?

+5
source share
3 answers

, , . , .NET Framework. .

, log4net , .

Visual Studio:

:

EDIT:

, , , :

+7

acoolaum, . , , . , , TCP/IP, , - TCP/IP.

, , . .

+2

, : , , WinForms, ?

, Watch Windows, , n- . , , UI, UI-, -, , .

.

+1

More articles:


All Articles