您好,我是独立顾问(Independent Advisor)Dexter,请让我来继续帮助您.
WinDbg中需要访问的Symbols服务器最近一段时间在大陆地区出现了网络访问异常导致了您遇到的问题,有条件的话,可以考虑使用代理来进行访问.
使用 ! anaylyze -v 出现下面的这种情况 请问是怎么回事呢?网上搜了很多是什么windbg不能访问网络,不能下载符号文件。想请教一下您!谢谢!
Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information.
Debugging Details:
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: NT!_DEVICE_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_IRP ***
*** ***
*************************************************************************
锁定的问题。 此问题已从 Microsoft 支持社区迁移。 你可投票决定它是否有用,但不能添加评论或回复,也不能关注问题。
您好,我是独立顾问(Independent Advisor)Dexter,请让我来继续帮助您.
WinDbg中需要访问的Symbols服务器最近一段时间在大陆地区出现了网络访问异常导致了您遇到的问题,有条件的话,可以考虑使用代理来进行访问.
嗯~路径设置没问题的,下面是我现在使用的设置截图.前段时间也是一直下载失败,后来用了代理好了~
您好,还是会出现之前说的错误。还是不行诶?
您好 我照着您说的做了 还是会出现 Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. 很多次。
您好,我是Jarl,一名独立顾问 (Independent Advisor) 和Windows 10的资深用户,很荣幸能再次为您提供技术支持。
根据您提供的讯息,可能您的WINDBG设置不正确哦。
请问您目前的Symbol Path位置是什么呢?
如果还有其他相关的问题,我会努力为您解答!
Jarl