

Moreover, this is how livekd prefers to set the symbol path if you allow it to automatically configure the path for you. I configured the symbol path using the canonical example (minus the hxxp mangling ): _NT_SYMBOL_PATH=srv*C: Symbols*hxxp:///download/symbols The _NT_SYMBOL_PATH environment variable is a user variable rather than a system variable, but I don't see why that would matter.


#LIVEKD COULD NOT RESOLVE SYMBOLS FOR NTOSKRNL.EXE WINDOWS#
I've downloaded the latest version of livekd (3.0) and the debugging tools for windows (server 2k3 R2).
