1

I'm attempting to debug a manual dump file of a 64bit w3wp process with 64bit Windbg (Version 6.10). The dump was taken with taskmgr. I can't get anything from the !clrstack command. Here is what I'm getting:

!loadby sos clr

!runaway

User Mode Time
  Thread       Time
  17:cf4       0 days 5:37:42.455

~17s

ntdll!ZwDelayExecution+0xa:

00000000`776208fa c3 ret

!clrstack

GetFrameContext failed: 1

What is GetFrameContext failed: 1?

Jeff B
  • 8,572
  • 17
  • 61
  • 140
user3404513
  • 11
  • 1
  • 2
  • Type the command || to verify what kind of dump you have. For .NET applications, this needs to be "full memory user mini dump". Also, run !threads to give an overview of all of the managed threads. You're currently pointing to thread #17 (~17s), but it may not be a managed threads. For native threads, you can use the k command to view the stack. – Dono Mar 11 '14 at 06:29
  • @Dono: task manager creates full memory dumps. For unmanaged threads, !clrstack usually says "Unable to walk the managed stack.", not "GetFrameContext failed". – Thomas Weller Mar 11 '14 at 11:56
  • It seems you're not alone, but there's no answer: http://stackoverflow.com/questions/7878112/how-to-i-resolve-getframecontext-failed-in-windbg – Thomas Weller Mar 11 '14 at 12:34
  • possible to make the dump available? – AR5HAM Apr 22 '15 at 01:06

2 Answers2

2

Use !dumpstack command instead of !clrstack. It usually works.

T.P.
  • 291
  • 2
  • 9
0

Try getting the "native" call stack by doing "k" and see what that gets you. Sometimes, the stack isn't quite right and the !ClrStack extension is pretty sensitive.

Remi Lemarchand
  • 863
  • 6
  • 4