Hi,
I use .kdfiles ALL the time, some other people here have had some initial
problems but I think we found the mapping file parser did not like an empty
line at the end of the file, I think the parser is not very robust. Ensure
there are not white spaces at the end of each line and that there are not
blank lines at the end.
Yours
Roger
Roger Coote,
Senior Design Engineer
PowerVR Technologies, A Division of Imagination Technologies Ltd
Home Park Estate, Kings Langley, Hertfordshire, WD4 8LZ, UK
phone :+44 (1923) 260511 fax :+44 (1923) 268969
direct :+44 (1923) 277274
mailto:xxxxx@powervr.com www.powervr.com
-----Original Message-----
From: Phil Barila [mailto:xxxxx@Seagate.com]
Sent: 29 August 2002 19:35
To: Kernel Debugging Interest List
Subject: [windbg] Re: Magic incantation to make .kdfiles *do* something?
“Sean Bullington” wrote in message news:xxxxx@windbg…
>
> Hrm everything looks OK in your setup… My file is simply called
> drvmap.ini, and looks like:
>
> map
> \Systemroot\system32\drivers\phmmini.sys
> D:\Host\kernel\build\chk_w2k\i386\phmmini.sys
>
> And my loading looks the exact same as yours:
> kd> .kdfiles d:\drvmap.ini
> KD file assocations loaded from ‘d:\drvmap.ini’
>
> The only difference seems to be that I’m using a serial connection,
> although I’ve used the same method over 1394.
> One error I’ve stumbled over is, if the pdb is in use by WinDBG, and you
> build, you’ll get the lovely error about not being able to create the
> pdb cause it is locked. And thus the final binary is not created. When
> the target machine reboots, the driver won’t be copied over the
> connection because the binary isn’t there (and there is no warning, etc.
> shown in WinDBG).
Sean,
Thanks for checking. I tried both serial and 1394, and couldn’t tell the
difference, except for speed. And I know I got a good build, because my
build environment sure complains when the pdb is in use, and besides, the
reason for the PDB mismatch was that I had a driver without the bug waiting
to be tranferred to the target, with a matching PDB, which no longer matched
the driver on the host. It was trying to load the PDB because I tried to
set a breakpoint on SeUlator!DriverEntry, but it couldn’t load the PDB, so
it couldn’t instantiate the BP.
Solved with the repair console, but I’d really like to get this working,
because I’m sure I’m going to do it again…
Hmmph.
Phil
–
Philip D. Barila
Seagate Technology, LLC
(720) 684-1842
—
You are currently subscribed to windbg as: xxxxx@videologic.com
To unsubscribe send a blank email to %%email.unsub%%