Topic

Kernel Logging

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #13924
    cjw94022
    Participant

    Does the kernel module provide any logging? If not, would it be easy to add logging into the kernel if the source code license is purchased?

    #13925
    Vadim Smirnov
    Keymaster

    The driver shares a substantial amount of code across various Windows versions, so currently, the only available tracing method is through DbgPrint, which is enabled only in debug builds. If you’re specifically asking about ETW traces, this type of logging hasn’t been implemented yet. However, it can certainly be added for driver builds on Windows 7 and later versions if needed.

    #14494
    iricah21
    Participant

    I’d be interested in this too. Even basic kernel-level logging would make troubleshooting a lot easier, especially when trying to figure out what’s happening without constantly attaching a debugger. If the source code is available under a suitable license, adding logging with printk() or the kernel’s pr_debug() macros should be possible, depending on how the module is structured. The main thing would be making the logs configurable so they don’t flood the kernel log during normal use!

    • This reply was modified 5 days, 11 hours ago by iricah21.
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.