调试功能测试（徽标） - 错误：测试超时等待内核调试器中断 [英] Debug Capability Test (Logo) - Error: test timed out waiting for the kernel debugger to break in

问题描述

Hello All，

Hello All,

我在使用串行端口连接运行调试功能测试时遇到此错误。连接很好，我可以使用内核调试器从主机到目标而没有任何问题。但是，在测试自动化下，我一直都会遇到这种失败。

I'm getting this error running the Debug Capability Test using serial port connection. The connection is good and I'm able to break in with kernel debugger from host to target without any problem. However, under test automation, I consistently get this failure.

调试器*正在进入。在收到错误消息之前，运行调试器的主机系统显示：

The debugger *is* breaking in. Prior to getting the error message, the host system running the debugger shows:

> ;>>状态更改事件3030，proc 3 of 64，str'< empty>'

>>> State change event 3030, proc 3 of 64, str '<empty>'

建立内核调试器连接。

符号搜索路径是：srv *

Symbol search path is: srv*

可执行搜索路径为：

....此时有一段很长的停顿时间。之后不久就发生了故障。

....at this point there is a long pause. The failure occurs shortly afterwards.

我尝试在本地网络上安装符号并将环境设置为指向本地符号但是，测试似乎试图使用网络定位符号无论如何。我的SUT和我的测试环境*没有*连接到互联网，
严格在私有域内。我认为符号搜索可能是延迟的来源。

I tried installing symbols on the local network and setting the environment to point to the local symbols but, it appears that the test tries to locate the symbols using the network anyway. My SUT and my test environment are *not* connected to internet and are strictly within the private domain. I thought the symbol search might be a source of the delay.

屏幕很快就会显示，但我甚至有一个捕获显示：

The screens go by quickly but, I even have a capture showing:

>>>事件statsu 6

>>> Event statsu 6

>等待返回0

....然后是寄存器转储。很明显，内核调试器*正在进入。为什么会出错？

....followed by register dumps. Clearly the kernel debugger *is* breaking in. Why the error?

推荐答案

其他细节....

Additional details....

我花了一些时间来尝试调试这个问题。

i've been spending some more time trying to debug this issue.

在"可执行搜索路径为："

The error occurs after a long pause after the line "Execuatable search path is:"

后面的长暂停后发生错误。然后是红色文字：

Then in red text:

错误：验证：测试超时等待内核调试器中断。[File：sdktools\debuggers\kdlt\testbin\kdlt.cpp，功能：KernelDebugLogoTest :: KernelDebugLogotest1，行：250]

Error: Verify: The test timed out waiting for the kernel debugger to break in. [File: sdktools\debuggers\kdlt\testbin\kdlt.cpp, Function: KernelDebugLogoTest::KernelDebugLogotest1, Line: 250]

在出现该错误消息后，屏幕显示：

After that error message, the screen shows:

***错误：找不到符号文件。默认导出ntkrnlmp.exe的符号 - Windows 8内核版本9200 MP（64触发器）免费x64

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Windows 8 Kernel Version 9200 MP (64 procs) Free x64

产品：服务器，套件：TerminalServer Datacenter SingleUserTS

Product: Server, suite: TerminalServer Datacenter SingleUserTS

建造者：9200.16384.amd64fre.win8_rtm.120725-1247

Built by: 9200.16384.amd64fre.win8_rtm.120725-1247

机器名称：

内核基数= 0xfffff803'd1009000 PsLoadedModuleList = 0xfffff803'd12d3a60

Kernel base = 0xfffff803'd1009000 PsLoadedModuleList = 0xfffff803'd12d3a60

---- ETC，ETC ----

---- ETC, ETC ----

显然，调试器*在超时错误消息后正在*中断被展示。调试会话中有更多信息和寄存器转储，然后测试报告失败：

Clearly, the debugger *is* breaking in right after the timeout error message is displayed. There's more info and register dumps typical of a debug session, then the test reports failure:

（红色）

EndGroup：KernelDebugLogoTest :: KernelDebugLogotest1 [失败]

EndGroup: KernelDebugLogoTest::KernelDebugLogotest1 [Failed]

非通过测试：

       KernelDebugLogoTest :: KernelDebugLogotest1 [失败]

       KernelDebugLogoTest::KernelDebugLogotest1 [Failed]

摘要：总计= 1，通过= 0，失败= 1，被阻止= 0，未运行= 0，已跳过= 0

Summary: Total=1, Passed=0, Failed=1, Blocked=0, Not Run=0, Skipped=0

我已将kdlt测试二进制文件复制到用作调试器的主机系统，并将SUT配置为串行调试，现在我可以从命令行本地运行测试并重复结果。这样做我已经能够通过修改"te"来获得通行证。
命令行选项，但没有任何一致的可重复性。通过删除"/ enableWttLogging"并设置"verbose = 0";我已经能够再次获得通过结果，而不是一致的结果。也许十分之一运行。

I've copied the kdlt test binaries to the host system used as the debugger and configured the SUT for serial debug and I can now run the test locally from the command-line and repeat the results. Doing this I've been able to get a PASS by modifying the "te" command-line options but, not with any consistent repeatability. By removing the "/enableWttLogging" and setting "verbose=0" I've been able to get passing results but again, not consistent results. Maybe 1 in 10 runs.

启动Windbg并附加到目标系统我注意到在"可执行搜索路径为："之后我总是得到一个长时间的停顿。但是，我没有成功减少初始化时间。

Launching Windbg and attaching to the target system I notice I always get a long pause after the "Executable search path is:" message but, I have not been successful at reducing that init time.

似乎测试是在实际发生入侵之前超时但是，我使用te命令行选项实验/ disableTimeouts或以其他方式影响时间不成功。

It seems that the test is timing out just prior to when the break-in actually occurs but, my experiments with the te command-line options to /disableTimeouts or otherwise influence timings have been unsuccessful.

我怀疑使用其他调试连接选项（1394，USB或NET）可以显着减少长延迟，但是在这个特定平台上，这些都没有目前是一个选项，除非我在两个系统
上安装支持的网络适配器但是，如果SERIAL是支持的选项，我不应该这样做。

I suspect the long delay can be significantly reduced using one of the other debug connection options (1394, USB, or NET) but, on this specific platform, none of these are currently an option unless I install supported network adapters on the two systems but, if SERIAL is a supported option, I shouldn't have to do that.

任何人？

**更新**

从度假回来，我又回到了再看这个问题。自从报告此问题以来，我已经在我的测试平台上运行/调试了所有其他必需的测试，并且我已经完成了这个特定测试，因为我唯一没有解决方案
。  任何人都使用串行调试接口成功吗？来自MS的任何人都有任何见解/建议吗？我特别感兴趣的是听到有关测试来源详细信息的人的说法：

Back from vacation and I'm back to looking at this issue again. Since reporting this issue, I've run/debugged all of the other required tests on my test platform and I'm down to this specific test as the only one I don't have a resolution for. Anyone else have success using serial debug interface? Anyone from MS have any insight/suggestions? I'd be especially interested in hearing from someone who has details on the test source:

[文件：sdktools\debuggers \ kdlt \testbin \ kdlt.cpp，功能：KernelDebugLogoTest :: KernelDebugLogotest1，Line：250]

[File: sdktools\debuggers\kdlt\testbin\kdlt.cpp, Function: KernelDebugLogoTest::KernelDebugLogotest1, Line: 250]

谢谢。

这篇关于调试功能测试（徽标） - 错误：测试超时等待内核调试器中断的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！