2016-05-15 20 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