Hi Folks,
I have not used the latest WinDBG in a long time. I am using what I think is
the latest version (5.00.2195.1163).
I used to be pretty good at getting WinDbg to work, but things have chanced
since then and I am not sure what I am doing wrong -
I used to set the source path and symbol patch via .srcpath and .sympath
commands (Atleast I remember it that way!)
I would always copy my driver and pdb file to a pre-designated folder and
make sure the debugger knew where it was via .sympath
Then I was fine, I could set break points and work.
Now with the new WinDbg, I *think* I have set the debuggers symbol path
correctly. (Currently set to %SystemRoot%\symbols, and that is where I copy
my driver and pdb file.
When I pull up the source file, and select a place to put a break, I get a
Violet/Pink breakpoint marker (What used to represent where the current
Instruction was when a break point was hit in the old windbg). When the
break is hit, a dialog complaining about the break pops up saying it cant
instantiate the break point, giving me different options (Including edit
breakpoints).
My question is:
What is it telling me, by break is never hit and the dialog gives me the
ability to skip it.
As a side I tried reloading the source files for my driver (.reload
DriverName) and it starts to reload, then says
Module Load: C:\Winnt\Symbols\DriverName (Could not open symbol file).
Could this mean my file is corrupt for some reason.
Also - How do I tell it where my source is for the driver. There is not
.srcpath command anymore (Or at least as far as I can tell). I noticed the
Path Mapping Pairs dialog. Is that it. I tried setting the Source to
C:\Winnt\symbols (Where I copy my Driver/pdb) and Mapped To my source
directory. This did not work. I also tried setting the “Default Path” on the
dialog to my source path, and that does not seem to work.
Thanks
-Chris
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com