Hi,
? I was looking at a connect(Socket) timeout which on Windows 7 expires after 21 seconds. So, what appeared to be a deadlock is now a proved fake positive. I have saved the memory file at that time and?!runaway 4?experiments show that elapsed time increases even when an attached process is being debugged.
? Is there a command that shows the effective execution time of a process without computing the time where is being debugged?
Regards,
? Calin
!runaway 3 shows the user and kernel times for the thread, which are the
actual CPU time consumed.
As far as elapsed time is concerned, it really is the amount of time since
the thread was created. I don’t know of a way to subtract from that the
amount of time that a thread is frozen because of the user mode debugger
(the clock is going to keep on ticking!). You might be able to create this
concept yourself with a debugger extension using the DebugExtensionNotify
callback (i.e. record the amount of time that the process is frozen and
write your own “!mythreadtimes” or something). Maybe someone else will have
a better idea…
-scott
–
Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Calin Iaru” wrote in message news:xxxxx@windbg…
Hi,
I was looking at a connect(Socket) timeout which on Windows 7 expires
after 21 seconds. So, what appeared to be a deadlock is now a proved fake
positive. I have saved the memory file at that time and !runaway 4
experiments show that elapsed time increases even when an attached process
is being debugged.
Is there a command that shows the effective execution time of a process
without computing the time where is being debugged?
Regards,
Calin