I was debugging a mini-filter I am building with the Vista WDK this morning,
and realized I should be useing !fltkd, unfortumately I keep getting the
following message, and a number of commands fail.
“*** Extension DLL(5278 Free) does not match target system(2600 Free)”
Can somebody shed light on this?
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
The message is mainly a legacy thing. In the old days extensions had to
match the system they were debugging and so they did version checks.
Nowadays such tying is discouraged and extensions are supposed to
automatically adapt to the target. The version checking hasn’t been
entirely cleaned out, so sometimes you get messages even when they don’t
matter.
However, if commands are failing it’s possible there’s still a version
dependency. What exact commands are failing and with what errors?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Monday, May 08, 2006 10:20 AM
To: Kernel Debugging Interest List
Subject: [windbg] fltkd, Vista WDK and Windbg
I was debugging a mini-filter I am building with the Vista WDK this
morning, and realized I should be useing !fltkd, unfortumately I keep
getting the following message, and a number of commands fail.
“*** Extension DLL(5278 Free) does not match target system(2600 Free)”
Can somebody shed light on this?
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Drew,
!fltkd.ctx in particular is failing, it just comes back with:
*** Extension DLL(5278 Free) does not match target system(2600 Free)
ctx [addr] [detail] Dump CONTEXT_NODE
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
The message is mainly a legacy thing. In the old days extensions had to
match the system they were debugging and so they did version checks.
Nowadays such tying is discouraged and extensions are supposed to
automatically adapt to the target. The version checking hasn’t been
entirely cleaned out, so sometimes you get messages even when they don’t
matter.
However, if commands are failing it’s possible there’s still a version
dependency. What exact commands are failing and with what errors?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Monday, May 08, 2006 10:20 AM
To: Kernel Debugging Interest List
Subject: [windbg] fltkd, Vista WDK and Windbg
I was debugging a mini-filter I am building with the Vista WDK this
morning, and realized I should be useing !fltkd, unfortumately I keep
getting the following message, and a number of commands fail.
“*** Extension DLL(5278 Free) does not match target system(2600 Free)”
Can somebody shed light on this?
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Just to be clear, you’re specifying a CONTEXT_NODE address, correct?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Monday, May 08, 2006 10:36 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] fltkd, Vista WDK and Windbg
Drew,
!fltkd.ctx in particular is failing, it just comes back with:
*** Extension DLL(5278 Free) does not match target system(2600 Free)
ctx [addr] [detail] Dump CONTEXT_NODE
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
The message is mainly a legacy thing. In the old days extensions had to
match the system they were debugging and so they did version checks.
Nowadays such tying is discouraged and extensions are supposed to
automatically adapt to the target. The version checking hasn’t been
entirely cleaned out, so sometimes you get messages even when they don’t
matter.
However, if commands are failing it’s possible there’s still a version
dependency. What exact commands are failing and with what errors?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Monday, May 08, 2006 10:20 AM
To: Kernel Debugging Interest List
Subject: [windbg] fltkd, Vista WDK and Windbg
I was debugging a mini-filter I am building with the Vista WDK this
morning, and realized I should be useing !fltkd, unfortumately I keep
getting the following message, and a number of commands fail.
“*** Extension DLL(5278 Free) does not match target system(2600 Free)”
Can somebody shed light on this?
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com