Re: Child display driver ... adding PnP crashes!

Regardless, though, `.reload modulename' (without needing a .reload /u)
should always be sufficient to cause a redetermination of what symbol files
should be used (at least for recent debugger versions, can't say about
ancient versions) - even if the debugger has already tried and failed to
load symbols and has failed back to export symbols.

If you use `.reload /u', you would need to manually recreate the module in
the debugger loaded module list (i.e. `.reload module=base,size') or it will
be gone forever and now show up in `lm' or any command that references
loaded modules using the debugger's internal list - at least, this is my
experience.

"Maxim S. Shatskih" <maxim@xxxxxxxxxxxxxxxx> wrote in message
news:%231vM6TkdGHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
It loads the kernel symbols 2 times - first on the very boot, and they
are
export symbols. Then, after determining the exact version using these
symbols,
it reloads the real-world symbols.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com

"Skywing" <skywing_NO_SPAM_@xxxxxxxxxxxxxxxxxxx> wrote in message
news:uxcseqedGHA.3348@xxxxxxxxxxxxxxxxxxxxxxx
Actually, I think the debugger will try to load symbols always if it is
using export symbols.

*** ERROR: Symbol file could not be found. Defaulted to export symbols
for
ntkrnlpa.exe -

*******************************************************************************
WARNING: Local kernel debugging requires booting with /debug to work
optimally.

*******************************************************************************
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Fri May 12 12:31:45.546 2006 (GMT-5)
System Uptime: 0 days 0:17:19.340
lkd> lm
start end module name
804d7000 806cd280 nt (export symbols) ntkrnlpa.exe

Unloaded modules:
f9b6c000 f9b75000 processr.sys
f9cc4000 f9cc9000 Cdaudio.SYS
f9699000 f969c000 Sfloppy.SYS
lkd> .reload nt
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for
ntkrnlpa.exe -
lkd> .symfix c:\symbols
lkd> .reload nt
lkd> lm
start end module name
804d7000 806cd280 nt (pdb symbols)
c:\symbols\ntkrnlpa.pdb\89C2A9EB56A74E2D8269AFD1D835BA331\ntkrnlpa.pdb

Unloaded modules:
f9b6c000 f9b75000 processr.sys
f9cc4000 f9cc9000 Cdaudio.SYS
f9699000 f969c000 Sfloppy.SYS

`.reload /u' is probably not what you will want and will remove the
module
entirely from the debugger's list.

"Maxim S. Shatskih" <maxim@xxxxxxxxxxxxxxxx> wrote in message
news:%23KBUWZddGHA.1436@xxxxxxxxxxxxxxxxxxxxxxx
Clearly indiacting that my kernel symbols have not been loaded. Why
does symfix not work for me? Do I need to upgrade WinDbg ( Current

Read my previous email more carefully.

.symfix does not reload anything. If you have the wrong symbols loaded
("export
symbols" or "no symbols") - then you must unload them:

.reload /u nt

and load the new ones after .symfix:

.reload nt

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com






.

Relevant Pages

  • Re: Child display driver ... adding PnP crashes!
    ... Try the `!sym noisy' command and then the `.reload nt' command and posting ... but this is what the debugger shows and then there is ... copy the SYS/DBG/PDB files of your driver there. ... the build target path itself - you will not be able to rebuild with the ...
    (microsoft.public.development.device.drivers)
  • Re: Child display driver ... adding PnP crashes!
    ... I think the debugger will try to load symbols always if it is ... lkd> .reload nt ... does symfix not work for me? ...
    (microsoft.public.development.device.drivers)
  • Re: Child display driver ... adding PnP crashes!
    ... It loads the kernel symbols 2 times - first on the very boot, ... lkd> .reload nt ... does symfix not work for me? ...
    (microsoft.public.development.device.drivers)
  • Re: WinDVD.Exe- Application Error
    ... I think though with a debugger you can ... Either from the windvd install cd or windows ... Just reload the files that are corrupt ...
    (microsoft.public.win2000.general)
  • Re: Debuggers
    ... post-mortem debugging you'd like to inspect local variables defined at the ... This can be seen with pdb, ... I agreed the idea to restart the debugger when an exception is trow. ... It could be feasible to let reload the file and restart. ...
    (comp.lang.python)