That's what I thought, and how it was working at one time. Well, it's been a
week of oh ****s, because ,kdfiles tain't working for me, on either signed
or unsigned drivers. Probably have something really stupid in my mapping
file.
Thanks for the confirmation guys.
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill Wandel
Sent: Thursday, May 06, 2010 6:12 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Debugging signed 64 bit drivers
If a debugger is attached then the driver does not need to be signed.
.kdfiles will load an unsigned driver. I do this all the time.
Bill Wandel
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Thursday, May 06, 2010 3:32 PM
To: Kernel Debugging Interest List
Subject: [windbg] Debugging signed 64 bit drivers
How is kdfiles affected when debugging such beasts? Will .kdfiles load a
freshly built unsigned driver or must it be signed or, must the boot or test
signing be set in the target? I stgrongly suspect the later.
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
__________ Information from ESET Smart Security, version of virus signature
database 5092 (20100506) __________
The message was checked by ESET Smart Security.
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
To unsubscribe, visit the List Server section of OSR Online at
ListServer/Forum
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
To unsubscribe, visit the List Server section of OSR Online at
__________ Information from ESET Smart Security, version of virus signature
database 5092 (20100506) __________
The message was checked by ESET Smart Security.