Windbg- Crash dump

Asked Mar 06 '16 at 08:31

Active Mar 07 '16 at 00:11

Viewed 182 times

I have IIS crash dump of a .net web application. After doing dumpstack I got call stack:

00000000028fe8c0 000007fe9b6f2fe5 (MethodDesc 000007fe99e41878 +0x105 ABC.dll!Unknown), calling (MethodDesc 000007fef7634de0 +0 System.Reflection.MethodBase.Invoke(System.Object, System.Object[]))
00000000028fe910 000007fe9a075b68 (MethodDesc 000007fe9a667460 +0x38 XYZ.dll!Unknown), calling (MethodDesc 000007fef7553ff8 +0 System.Activator.CreateInstance[[System.__Canon, mscorlib]]())

I want to know actual method which stack pointing to. How to get this using windbg?

edited Mar 07 '16 at 00:11

seva titov

11,720
2
35
54

asked Mar 06 '16 at 08:31

Ramaprasad Upadhyaya

use !clrstack from sos.dll to see more – magicandre1981 Mar 06 '16 at 09:08
Don't use dumpstack. As has been pointed out, use !sos.clrstack, !sosex.mk, or just the debugger "k" command. The latest debuggers know how to interpret the managed stack. – Steve Johnson Mar 07 '16 at 00:30
@SteveJohnson: really? Since which version is that feature included? – Thomas Weller Mar 07 '16 at 10:39
@SteveJohnson Yes, do tell! – Marc Sherman Mar 07 '16 at 14:48
I'm sorry, I was mistaken. This feature is not included in the debuggers. – Steve Johnson Mar 08 '16 at 15:41
Did !sos.clrstack or !sosex.mk do what you needed? – Thomas Weller Mar 18 '16 at 10:11
Hi Issue was something else. I forgot to load pdb files which caused the issue. After loading, everything was fine. – Ramaprasad Upadhyaya Mar 22 '16 at 05:37
Ok, maybe you want to delete the question then – Thomas Weller May 13 '16 at 06:24

Windbg- Crash dump

0 Answers0