如何我解决GetFrameContext失败的Windbg [英] How to I resolve GetFrameContext failed in Windbg

问题描述

我调试使用完整的崩溃转储和WinDBG的一个.NET 4.0的Web应用程序。我似乎能够得到的一切的所有版本但是相匹配，当我试图让我得到的线程

I'm debugging a .NET 4.0 web application using a full crash dump and Windbg. I seem able to get all the versions of everything to match up however when I try to get the managed stack trace of all the thread I get

操作系统线程ID：0x7cd4（13） 儿童SP IP呼叫网站 GetFrameContext失败：1

OS Thread Id: 0x7cd4 (13) Child SP IP Call Site GetFrameContext failed: 1

有关我所有的管理线程。任何想法，我做错了，我怎么能解决这个问题？

For all of my managed threads. Any ideas what I'm doing wrong and how I can fix it?

推荐答案

我也收到这个错误，但我注意到，运行！DumpStack确实给我一丝的时候！ClrStack没有。

I was also getting this error, but I noticed that running !DumpStack does give me a trace when !ClrStack does not.

根据该<一href="https://social.msdn.microsoft.com/Forums/vstudio/en-US/e79fb093-7fea-4b01-89a4-7d10c911bff6/what-is-clrclrsemaphorewait-?forum=clr"相对=nofollow> 该链接可能只是已定，但不运行的线程。换句话说不一定是一个问题。我不知道为什么clrstack命令不工作，虽然，可能是一个SOS错误？

According to this link it could just be a thread that has been scheduled but is not running. In other words not necessarily a problem. I'm not sure why the clrstack command doesn't work though, possibly an sos bug?

0:037> !clrstack
OS Thread Id: 0x57cc (37)
Child SP         IP               Call Site
GetFrameContext failed: 1
0:037> !dumpstack
OS Thread Id: 0x57cc (37)
Child-SP         RetAddr          Call Site
000000000772f688 000007fefdb210dc ntdll!NtWaitForSingleObject+0xa
000000000772f690 000007fef5ca36ca KERNELBASE!WaitForSingleObjectEx+0x79
000000000772f730 000007fef5ca3a97 clr!CLRSemaphore::Wait+0xaa
000000000772f7f0 000007fef5ca3c20 clr!ThreadpoolMgr::UnfairSemaphore::Wait+0x140
000000000772f830 000007fef5cb21ff clr!ThreadpoolMgr::NewWorkerThreadStart+0x2a7
000000000772f8d0 000007fef5cb0582 clr!ThreadpoolMgr::WorkerThreadStart+0x3b
000000000772f970 00000000778d652d clr!Thread::intermediateThreadProc+0x7d
000000000772fb30 0000000077b0c521 kernel32!BaseThreadInitThunk+0xd
000000000772fb60 0000000000000000 ntdll!RtlUserThreadStart+0x1d

这篇关于如何我解决GetFrameContext失败的Windbg的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！