Re: how can I kernel debug NDIS IM driver "passthru" example in VMWare?! by David
David
Sun Dec 23 11:09:54 CST 2007
First, I assume, you are attaching Windbg to the Virtual Machine via a named
pipe and *not* kernel debugging the Host machine. I will also assume that
Windbg is attaching correctly and that you have symbols setup, etc., etc.
and that kernel debugging is working correctly. If not, then, you need to
get to that point.
Make sure that you are using the BU (deferred breakpoint) style and not BP
if you are setting the breakpoint and expecting it to get 'reset' correctly
if the driver is loaded dynamically.
Break into the debugger and check if your module and symbols are even
loaded.
kd> lmvmPASSTHRU
should tell you lots about PASSTHRU.
use the NDISKD extensions to determine if your driver is bound to anything
and has exported any miniports.
kd> !ndiskd.protocols
will show you lots. PASSTHRU and your virtual miniport should show up in
that listing.
Make sure your breakpoints are 'enabled'.
kd> bl
will list your breakpoints and if they don't have an 'e' in them, they are
not enabled.
Good Luck,
Dave Cattley
Consulting Engineer
"lostlander" <lostlander.tom@gmail.com> wrote in message
news:4cfd6177-6d4e-45a6-ad6f-f865b0c3b1f9@e25g2000prg.googlegroups.com...
> After I install the "passthru" in vmware succesfully, then connect to
> vmware using windbg, and set some breakpoint on "PtReceivePacket" or
> MP* functions, it simply doesn't stop there.
>
> I use bridged mode in vmware for the NIC.
>
> I can surf the internet in the vmware machine, does this mean that the
> packet doesn't go through "passthru"??
>
> Thanks for any reply.