Debugging deadlock

[intelgg]

I am using CVF 6.5.A on Windows 2000 / Pentium 3.
Sometimes when using breakpoints while debugging,
I get the following in the Debug window:

DBG: Break command failed within 3 seconds.
DBG: Potential deadlock. Soft broken.

Then I have to stop and restart debugging.
What's the cause and how do I stop this from hapenning.
Thank you

[Steven_L_Intel1]

This is a new one on me! I've never seen that before and have no clue as to what the problem might be. All I can guess is that there's either some process on your system that's monopolizing the CPU (maybe your application) or there's an OS bug.

Steve

[gfthomas8]

Take a look at John Robbins' 'Debugging Applications' (Microsoft Press, 2000), Chapter 12, entitled 'Multithreaded Deadlocks.'

Good luck,
Gerry T.

[Deleted_U_Intel]

You are probably debugging a CPU intensive thread or other thread that is thrashing the system somewhat... The debugger is being dumb. If you raise the priority of the debugger to "above normal" with task manager, it should all work fine again... (The debugger gets confused if it takes too long to break into the target process, and apparently, the "too long" timing starts *before* the break has been delivered to the target process, so if the debugger is delayed in running, the timer pops!)