• Re: New to WindDbg - Synchronizing Symbols

    From Mayur Aggarwal@21:1/5 to All on Mon Aug 15 04:54:33 2022
    ************************************************************************* *************************************************************************
    *** ***
    *** ***
    *** 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!_KPRCB ***
    *** *** ************************************************************************* *************************************************************************
    *** ***
    *** ***
    *** 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!_KPRCB ***
    *** *** ************************************************************************* *************************************************************************
    *** ***
    *** ***
    *** 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!_KPRCB ***
    *** *** ************************************************************************* Probably caused by : ntoskrnl.exe ( nt+3f5e40 )

    Followup: MachineOwner
    ---------


    !sym noisy
    noisy mode - symbol prompts on

    .sympath srv*Unknown format characterUnknown format control character DBGHELP: Symbol Search Path: srv*C:\Users\Mayur Aggarwal\AppData\Roaming\windbgtool\symbols*http://msdl.microsoft.com/download/symbols
    DBGHELP: Symbol Search Path: srv*C:\Users\Mayur Aggarwal\AppData\Roaming\windbgtool\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*%APPDATA%\WinDbgTool\Symbols*http://msdl.microsoft.com/download/symbols
    Expanded Symbol search path is: srv*%appdata%\windbgtool\symbols*http://msdl.microsoft.com/download/symbols

    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred srv*%APPDATA%\WinDbgTool\Symbols*http://msdl.microsoft.com/download/symbols
    There was a type mismatch between a binary and an application

    Got this error in .dmp file. Can someone help?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)