The stop count and trivia

re: The stop count and trivia

j.stagner — Thu, 23 Mar 2006 15:47:22 GMT

I notice that Mdbg tracks the stop count itself, so I guess that's the recommended way?

I know I'll need async-break eventually, I just haven't implemented it yet, as there are so many "interesting" things to do with a debugger.

ICD is huge, and has a whole lot of power and functionality, and I'm just taking it a step at a time ;)

Once again, very glad that you have an active blog!!!

Interesting Finds

Jason Haley — Thu, 23 Mar 2006 12:43:15 GMT

re: The stop count and trivia

Mike Stall - MSFT — Thu, 23 Mar 2006 06:49:22 GMT

IsRunning just yields a bool, so you can't use it to determine the stop-count.
IsRunning is also very dangerous in a multi-threaded scenario because the results may get invalidated by another thread. Similar issues with IsBadReadPtr().

Your UI will probably need some sort of async-break event. Somebody's going to write an infinite loop and want to figure out why their program is hung. They async-break, look at the call stacks and hopefully then notice the problem.

re: The stop count and trivia

j.stagner — Thu, 23 Mar 2006 04:40:12 GMT

Is this stop count reflected in the results from ICorDebugProcess.IsRunning ?

I should probably know the answer to this I suppose, but the debugger UI I am building doesn't currently allow the user to stop the debuggee without actually terminating and doesn't do so itself (it only stops on debug events) so it hasn't been an issue so far.