WEC2013 .kdmp文件中没有可用的调用堆栈信息？ [英] No call stack information available in WEC2013 .kdmp file?

问题描述

大家好，



我们有一个.kdmp文件（在WEC 2013上）报告NDIS崩溃。我们怀疑我们的以太网驱动程序使用无效参数调用NDIS函数。为了找出哪个源代码行，我们希望在崩溃时有一个调用堆栈。不幸的是，
将.kdmp文件加载到Platform Builder中时，我们看不到调用堆栈。

事实证明，堆栈的内存区域在kdmp文件中不可用。我们希望堆栈可用，因为它将成为线程环境块（TEB）的一部分。

我们在HKLM \ System \ ErrorReporting \DumpSettings中试验了DumpType但这不是似乎获得了有关违规线索的更多数据。



是否有人建议如何继续？



提前致谢，b
$
Marcel

Hi all,

We have a .kdmp file (on a WEC 2013) system which reports a crash in NDIS. We suspect our ethernet driver to call an NDIS function with invalid arguments. In order to find out from which source line, we want to have a call stack at the time of the crash. Unfortunately, when loading the .kdmp file into Platform Builder, we do not see the call stack.
It turns out that the memory area of the stack is not available in the kdmp file. We expect the stack to be available as this would be part of the Thread Environment Block (TEB).
We experimented with the DumpType in the HKLM\System\ErrorReporting\DumpSettings but this does not seem to get more data about the offending thread.

Does anyone have a suggestion on how to proceed?

Thanks in advance,

Marcel

推荐答案

嗨Marcel，

Hi Marcel,

这是我们（以及其他一些MVP）很久以前向微软报告的已知错误。 MS CE支持团队目前正在收集信息并尝试重现该问题（他们说，这一切似乎都适用于CEPC）。希望我们很快就能获得
的修复。

This is a known bug that we (and some other MVPs) have reported a long time ago to Microsoft. The MS CE support team is currently gathering information and trying to reproduce the issue (it all seems to work on CEPC they say). Hopefully we will have a fix soon.

我假设您使用的是ARM平台（i.MX6 IIRC），这样可以帮助MS团队。如果您与MS打开另一个支持事件，那么它们也会有所帮助，因此他们知道这不仅仅是一次事件，而是这个bug影响了许多客户。

I assume you are on an ARM platform (i.MX6 IIRC), so that would help the team at MS. What would also help is if you open another support incident with MS so they know it's not just a single occurrence but that this bug affects many customers.

这篇关于WEC2013 .kdmp文件中没有可用的调用堆栈信息？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！