Any suggestions are greatly appreciated.
Rich Lander
CLR Program Manager
Microsoft
> No, sorry. I wish I did. Part of the problem is that it's
> intermittent and I don't know under what circumstances it's
> happening. I was hoping someone could give me some things to look for
> in my code as possible suspects.
The first thing to analyse this would be to take a dump when the hang
occures (If it is reproducable on your box and not only in production /
customer side, then you may also use interactive debugging).
Download the "Debugging Tools for Windows", and use windbg / cdbg to dump
your process.
You may also use the "adplus.vbs" which utilizes cdbg and provides a various
cmd-line args.
Just execute: "adplus -hang -p 1234" where 1234 is the PID of your app. When
the process is finished, you find a .dmp file within a subfolder of the
installation directory of the Debugging Tools for Windows.
Load this dump into windbg and look at the (managed and unmanaged) callstack
of the executing threads. When it comes to unmanaged debugging (basically
into mscorwks) you should ensure that you have the symbol server configured.
There is a very good msdn blog that covers that topic:
If you have further questions feel free to ask!
GP
"dlgproc" <dlg...@discussions.microsoft.com> wrote in message
news:4A1C646A-0C6F-4201...@microsoft.com...