2016-05-15 57 views
0

在WinDbg中:文件 - >符号文件路径?设置我试图使这个例子 Srv*c:\symbols*https://msdl.microsoft.com/download/symbols 这个路径文件后: https://msdn.microsoft.com/en-us/library/windows/hardware/mt269367 在第5节第2步,当我键入.reload /f失去了调试器连接到 目标我设置的路径。 如果我没有设置符号文件路径,WinDbg也会在同一点进行破解。.reload命令后连接丢失到目标

对我来说,似乎windbg失去了与目标的连接,并没有得到它 重新建立。即使我在VM上重启目标系统。

有人可以告诉我发生了什么事,我做错了什么或为什么会发生这种情况?

我正在使用VMWare Player。我的主机和目标操作系统是Windows 10 Pro。 VMWare被配置为在NAT中使用网络。 Echo驱动程序已成功安装。

在下面你可以看到WinDbg的日志:

<Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64 
Copyright (c) Microsoft Corporation. All rights reserved.> 

<Using NET for debugging> 
<Opened WinSock 2.0> 
<Waiting to reconnect... 
<Connected to target 192.168.2.107 on port 50000 on local IP 192.168.2.107.> 
<Connected to Windows 10 10586 x64 target at (Sat May 14 22:41:26.873 2016(UTC + 2:00)), ptr64 TRUE> 
<Kernel Debugger connection established.> 

<************* Symbol Path validation summary **************> 
<Response       Time (ms)  Location> 
<Deferred          > 
<Srv*c:\symbols*https://msdl.microsoft.com/download/symbols> 
<Symbol search path is: > 
<Srv*c:\symbols*https://msdl.microsoft.com/download/symbols> 
<Executable search path is: > 
<Windows 10 Kernel Version 10586 MP (1 procs) Free x64> 
<Product: WinNt, suite: TerminalServer SingleUserTS> 
<Built by: 10586.306.amd64fre.th2_release_sec.160422-1850> 
<Machine Name:> 
<Kernel base = 0xfffff801`68a78000 PsLoadedModuleList = 0xfffff801`68d56cd0> 
<Debug session time: Sat May 14 22:41:25.623 2016 (UTC + 2:00)> 
<System Uptime: 0 days 0:06:44.196> 
<Break instruction exception - code 80000003 (first chance)> 
<*******************************************************************************> 
<*                    *> 
<* You are seeing this message because you pressed either     *> 
<*  CTRL+C (if you run console kernel debugger) or,      *> 
<*  CTRL+BREAK (if you run GUI kernel debugger),       *> 
<* on your debugger machine's keyboard.          *> 
<*                    *> 
<*     THIS IS NOT A BUG OR A SYSTEM CRASH      *> 
<*                    *> 
<* If you did not intend to break into the debugger, press the "g" key, then *> 
<* press the "Enter" key now. This message might immediately reappear. If it *> 
<* does, press "g" and "Enter" again.           *> 
<*                    *> 
<*******************************************************************************> 
<nt!DbgBreakPointWithStatus:> 
<fffff801`68bbfed0 cc    int  3> 
<kd> !sym noisy> 
<noisy mode - symbol prompts on> 
<kd> .symfix> 
<DBGHELP: Symbol Search Path: srv*c:\symbols*https://msdl.microsoft.com/download/symbols> 
<DBGHELP: Symbol Search Path: cache*;SRV*https://msdl.microsoft.com/download/symbols> 
<DBGHELP: Symbol Search Path: cache*;SRV*https://msdl.microsoft.com/download/symbols> 
<kd> .sympath+ C:\echo\kmdf\driver\AutoSync> 
<DBGHELP: Symbol Search Path:cache*;SRV*https://msdl.microsoft.com/download/symbols;c:\echo\kmdf\driver\autosync> 
<DBGHELP: Symbol Search Path:cache*;SRV*https://msdl.microsoft.com/download/symbols;c:\echo\kmdf\driver\autosync> 
<Symbol search path is: srv*;C:\echo\kmdf\driver\AutoSync> 
<Expanded Symbol search path is:cache*;SRV*https://msdl.microsoft.com/download/symbols;c:\echo\kmdf\driver\autosync> 

<************* Symbol Path validation summary **************> 
<Response       Time (ms)  Location> 
<Deferred          srv*> 
<OK            C:\echo\kmdf\driver\AutoSync> 
<kd> .sympath> 
<Symbol search path is: srv*;C:\echo\kmdf\driver\AutoSync> 
<Expanded Symbol search path is: > 
cache*;SRV*https://msdl.microsoft.com/download/symbols;c:\echo\kmdf\driver\autosync> 
<> 
<************* Symbol Path validation summary **************> 
<Response       Time (ms)  Location> 
<Deferred          srv*> 
<OK            C:\echo\kmdf\driver\AutoSync> 
<kd> .reload /f> 
<? Retry sending the same data packet for 64 times.> 
<The transport connection between host and kernel debugger and target Windows seems lost.> 
<please try resync with target, recycle the host debugger, or reboot the target Windows.> 
<...Retry sending the same data packet for 128 times.> 
<...Retry sending the same data packet for 192 times.> 
<...Retry sending the same data packet for 256 times.> 

问候。

回答

0

问题解决。 将虚拟机设置从以太网更改为COM。 我还通过使用this网站进行设置,将bcdedit调试设置更改为COM端口。 现在我可以调试并重新载入符号或驱动程序。

+0

我有nat和我有失去连接的问题,然后根据谷歌我改变了主机只有自然,然后连接失去的问题似乎已经消失应该值得尝试(净是看好,似乎更快比com的谷歌)回发如果是值得的努力,如果你尝试并成功 – blabb

+0

你有一个教程如何设置环境的链接?我拥有的不是很好。当我尝试时,它不适合我。这就是我选择COM端口的原因。 – MarksSO

+0

在vmware网络设置中选择仅主机单选按钮,在主机中执行ipconfig并从目标中找到vmnet1 ipv4地址ping如果没有问题,只需按照bcdedit/dbgsettings上的windbg bcdedit/debug文档:net ipaddr:== xxx port == XXX一个密钥将被自动生成使用它在像windbg.exe这样的主机上的批处理文件中“-k net:port = 55555,Key = – blabb