Myself and a colleague have recently started using wndbg. After a few
initial teathing troubles I managed to get everything working how I wanted,
my colleague however is having problems being able to see the symbols for
the driver he is working on. We have almost identical setups - debugging
drivers on a target PC over the serial port.
Both of us have our .sys built by the same build process (combination of
several pre-built libraries, I have also checked the build logs and they
have the same compiler and linker options) and residing in a similar
directory on our individual network home drive that is controlled by our
version control system. We both have the symbol path set to point to this
directory. My symbols work, his don’t. If I log into his system and try to
use it, my symbols work, so it doesn’t look like a windbg installation
problem on his host PC.
I have read some of the previous symbol threads on this list, and thought
!sym noisy might cast some light on the matter, so I tried it, but wndbg
complains about the version of kdextx86 by saying it uses the old 32 bit
extension API, and then doesn’t recognise the sym extension. The version of
kdextx86 is the one that came with the DDK I am using and it is the win2k
free build one, which , again is what I am using.
Any ideas at all would be appreciated, as I am getting a bit fed up with
this, not to mention my colleague.
Thanks!
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com