My esteemed colleagues -
I used USERDUMP.EXE to snatch a snapshot of a process, and am looking at the
resulting DMP file. Problem is, when i look at the call stack window, it always
looks.. well.. empty. (See shortcallstack.jpg in the ZIP file - it's one line
with three hex
numbers on it.)
This is true for all the threads i checked but one. They are all labelled
"Stopped" (see threads.jpg in the ZIP file). The one marked Running gives me a
but in this case not that useful stack backtrace - the one for the thread which
was called by WinNT to register the service. It just sits and waits until the
end of time... not interesting.
I don't believe that some 10 threads all have done nothing - this is a service
that's been running long enough to get in trouble! What do i need to do to see
the correct call stack for these threads?
Note that i tried using the thread dialog, pressing Freeze All, pressing Select
for one thread, then hitting the Call Stack button. I get the results you see
What to do, what to do? Thanks in advance...
i There's a Cross _|_
r h to bridge |
c the Great Divide.. |
Rich Pennenga -- Voice/Fax (732) 817-5927
Avaya Communication, formerly the Enterprise Networks unit of Lucent
Rm 2B-530A, 101 Crawfords Corner Road
Holmdel, NJ 07733 -- http://sjbcs.web.lucent.com/~dween