[sn0w]

i have no idea. tested, encountered the same. probably,- because you should attach during boot selection as when debugging with VisualDDK project

[sn0w]

VisualDDK configured to query MS sym svrs for modules seen first time, and to load for all mods.

but solved, i’d unexpected this way: .reload /f /d /v executed too fast, but finally did nothing

VisualDDK symbol path is set to: c:Symbols
Visual studio symbol cache is set to: C:Symbols_studio (VS concats this path with trailing “MicrosoftPublicSymbols”)

symbol load began to work properly when ive copied content from c:symbols to c:symbols_studioMicrosoftPublicSymbols

[sn0w]

symbol path is set. and there is a correct symbols, but why it cant see them

[sn0w]

hi! i’ve encountered with the same problem.both host and target are configured as well as it described in manuals: host – win7 x86, VS2010, visualddk 1.5, vmware 7.1. target – xp sp3 with installed virtualKD.

when i’m attaching via visualstudio’s kernel-mode connection transport, and “Loading kernel symbols” dialog appears – then error messages begins with the each pdb module currently processing – “Cannot load _path_to_pdb – unregistered class” (path to symbol store is set and it is correct), so what could happen?

[Author]

Posts