windbg

How can I learn WinDbg? (re: seemingly simple hung process)

I'm trying to determine why a process is hanging and am learning about various tools such as Process Explorer, Process Monitor, and WinDbg. Anyways, I'm trying to use WinDbg and after attaching to my process the debugger says this: (1e9c.1128): Break instruction exception - code 80000003 (first chance) eax=7ffda000 ebx=00000000 ecx=000...

Deadend whilst Debugging Silverlight with WinDBG and SOS

I'm new to WinDBG. I'm looking for the cause of a memory leak and I've got as far as my current knowledge can take me. My MVVM App is leaking MyLovelyView objects. In WinDBG I run !dumpheap -type MyLovelyView and get the following: Address MT Size 05f2a978 0bc948d4 12 05f39638 04d51114 36 05f398d4 04d2...

Debugging dump of 32-bit process captured on 64-bit machine

I recently received a 64-bit crash dump from a customer. Our processes are all 32-bit, but the customer's machine is running x64 Server 2008. Visual Studio (both 2008 and 2010 Express) is telling me that I have to use the 64-bit version of MSVSMON.EXE, which I can't because I don't have a 64-bit machine. I'm pretty sure there's a way t...

Use WinDbg to Write Contents of Managed Byte[] to File

I have a crash dump from a production server that shows an OutOfMemoryException. The exception itself is not relevant here. I happened to run a !dso to view the stack objects: 0:042> !dso OS Thread Id: 0x1014 (42) ESP/REG Object Name 246eeb24 109a21bc System.UnhandledExceptionEventHandler 246eeb2c 39083998 System.Runtime.Remoting.P...

Post mortem minidump debugging In windbg -- what causes <memory access error> for heap memory?

I'm looking at a crash dump. Some variables seem perfectly viewable in windbg, while others just say "memory access error". What causes this? Why do some variables have sensical values while others simply list ? It appears that all the problems are associated with following pointers. I'm certain that while many of these pointers are uni...