Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTDEV

Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Debugging NDIS Drivers

OSR_Community_UserOSR_Community_User Member Posts: 110,217
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

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    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:[email protected]]
    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: [email protected]
    To unsubscribe send a blank email to $subst('Email.Unsub')
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Kernel Debugging 13-17 May 2024 Live, Online
Developing Minifilters 1-5 Apr 2024 Live, Online
Internals & Software Drivers 11-15 Mar 2024 Live, Online
Writing WDF Drivers 20-24 May 2024 Live, Online