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

Before Posting... Please check out the Community Guidelines in the
Announcements and Administration Category, below.

minifilter driver logging

Hi,

I have been working for a few months on my first minifilter driver, and I am currently using "DbgPrint" and "DebugView" for logging.
I found "DebugView" not very convenient to work with as it consumes a lot of CPU when loaded and because I need to manually run it in order for logging to be stored to a file.
Is there a more convenient infrastructure for driver logs? Or maybe is there a way to capture "DbgPrint" in user space?
I am looking for something which can always store log messages to a file for later analysis and will not have that much affect on CPU.
Also, what is the common approach for driver logging for debug and release?

Thanks

Comments

  • Don_Burn-2Don_Burn-2 Posts: 1,620
    I'm not sure DebugView consumes much, but DbgPrint definitely can add a lot
    of overhead. You might look at WPP tracing which has low overhead
    https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/wpp-softwa
    re-tracing since it stores the binary values instead of doing a full
    "printf" implementation.

    Of course if you are actually debugging the driver, then DbgPrint and using
    WinDbg to allow full debugging is the way to go.


    Don Burn
    Windows Driver Consulting
    Website: http://www.windrvr.com




    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
    xxxxx@lists.osr.com
    Sent: Tuesday, September 12, 2017 12:46 PM
    To: Windows File Systems Devs Interest List <xxxxx@lists.osr.com>
    Subject: [ntfsd] minifilter driver logging

    Hi,

    I have been working for a few months on my first minifilter driver, and I am
    currently using "DbgPrint" and "DebugView" for logging.
    I found "DebugView" not very convenient to work with as it consumes a lot of
    CPU when loaded and because I need to manually run it in order for logging
    to be stored to a file.
    Is there a more convenient infrastructure for driver logs? Or maybe is there
    a way to capture "DbgPrint" in user space?
    I am looking for something which can always store log messages to a file for
    later analysis and will not have that much affect on CPU.
    Also, what is the common approach for driver logging for debug and release?

    Thanks

    ---
    NTFSD is sponsored by OSR


    MONTHLY seminars on crash dump analysis, WDF, Windows internals and software
    drivers!
    Details at <http://www.osr.com/seminars>;

    To unsubscribe, visit the List Server section of OSR Online at
    <http://www.osronline.com/page.cfm?name=ListServer>;
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!