Debugging NDIS Drivers

NTDEV
1

Hi!

Currently, I am writing an NT Intermediate NDIS Driver. I have a few
questions :

  1. Is it possible to do source level debugging in NDIS Drivers? If yes then
    how to achieve the settings. I have done source-level debugging in
    normal kernel-mode drivers before, but when I use that set up (Using WinDBG)
    and set a breakpoint in the driver source file, the break point
    is instantiated the first time but when try to step-over etc. the context
    is lost and an exception (Blue Screen) occurs after Go. I’m at a loss
    to explain how that could happen!

  2. Can I allocate another Packet Pool in the NT Intermediate NDIS Driver. A
    Bug-check occurs if I try to do so.

The NT symbols are ok since the BP is instantiated.

Thanks in advance.

Best Regards,

Sameer Kohli

2

Hi Sameer,

  1. Yes, debugging an Ndis driver is the same as debugging any kernel mode
    driver. You can source level debug any driver that you have the source for.
    When you hit the breakpoint below, does your source window open, with the
    highlight on the line that the breakpoint is on? If not, then you could have
    a symbol mismatch problem. Are you using the current debugger? There have
    been problems with some versions of WinDBG in the past. What OS are you
    trying to debug? This sounds like a debugger setup/version issue. It has
    nothing to do with NDIS.

  2. Yes. You can allocate a packet pool in an intermediate driver. What is
    the bug check you are getting?

Jim Mateer

-----Original Message-----
From: Sameer Kohli [mailto:xxxxx@ipolicynet.com]
Sent: Monday, May 08, 2000 1:29 AM
To: NT Developers Interest List
Subject: [ntdev] Debugging NDIS Drivers

Hi!

Currently, I am writing an NT Intermediate NDIS Driver. I have a few
questions :

  1. Is it possible to do source level debugging in NDIS Drivers? If yes then
    how to achieve the settings. I have done source-level debugging in
    normal kernel-mode drivers before, but when I use that set up (Using WinDBG)
    and set a breakpoint in the driver source file, the break point
    is instantiated the first time but when try to step-over etc. the context
    is lost and an exception (Blue Screen) occurs after Go. I’m at a loss
    to explain how that could happen!

  2. Can I allocate another Packet Pool in the NT Intermediate NDIS Driver. A
    Bug-check occurs if I try to do so.

The NT symbols are ok since the BP is instantiated.

Thanks in advance.

Best Regards,

Sameer Kohli

You are currently subscribed to ntdev as: xxxxx@MICROSOFT.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)