windows - Determine thread wait time in WinDbg with user-mode dump -


Is there any way to WinDbg, after determining that a date / time is a Windows thread for WaitForSingleObjects or waitformultipleObjects ?

I know how to do this in kernel debugging (using ! Thread ), but I do not know how to do this in user-mode debugging.

In WinDbg, you ! Runaway can use to get thread time:

 ! Runaway! Runaway 1   

(user time)

 ! Runaway 2   

(kernel time)

  runaway 4   

(elapsed time)

(You will find these documents as some places of 0, 1 and 2, but they do not work in my experience, maybe it depends on WinDbg version or some things ...)

You can calculate the time, the suspended spending by reducing the kernel time from the user of a thread and its time, but unfortunately I do not know in any way write WinDbg plugin In the area of ​​garden) get WinDbg to your advantage.

If you are not set to WinDbg, you can use it to get the same information. When you right-click a process and select the Thread tab in the Properties dialog, you get a list of all the threads in the process. Choosing a specific thread will reveal information at the same time, among other things.

Comments

Popular posts from this blog

qt - switch/case statement in C++ with a QString type -

python - sqlite3.OperationalError: near "REFERENCES": syntax error - foreign key creating -

Python's equivalent for Ruby's define_method? -