Check out ADPlus - http://support.microsoft.com/kb/286350
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Greg Keogh
Sent: Wednesday, 21 July 2010 4:44 PM
To: 'ozDotNet'
Subject: Unable to diagnose a crash
Folks, we have a random crash in our new r
Crash course in windbg:
start app
windbg.exe
- Attach to Process (menu)
(the rest are commands in the small command line at the bottom):
.loadby sos mscorwks(there is a . dot at the start)
sxe clr
g
It will automatically stop at _every_ .Net exception. You might find lots
and be scared of yo
Corneliu, Nick, I use windbg a few times a year to find elusive problems. I
was hesitant to attach windbg to a live server process that gets a fair bit
of traffic. The crash only occurs at daily intervals, so it's not feasible
for someone to sit 24x7 and keep typing 'g' and watching for the guilty
Greg,
If you don't feel like pressing go execute this:
sxi av
sxe -c "!pe;!clrstack;gc"
g
Just sit next to it in case it does break but otherwise it should just print
all exceptions, their call stacks and then immediately continue.
Corneliu.
On Thu, Jul 22, 2010 at 8:10 AM, Greg Keogh wrote
