Repository navigation
Replies: 1 comment 1 reply
|
For the kernel driver logs, enable Dokan's driver debug mask and capture kernel debug output. They are not written to the console. From an elevated Command Prompt/PowerShell, run the # normal driver tracing
dokanctl.exe /d 1
# or all current categories: default (1) + lock (2) + oplock (4)
dokanctl.exe /d 7The accepted range is Then capture it with either:
The reason the ordinary console shows nothing is visible in KdPrintEx((DPFLTR_IHVDRIVER_ID,
DPFLTR_TRACE_LEVEL,
"[dokan2]" ...));https://github.com/dokan-dev/dokany/blob/master/sys/util/log.h That is kernel debug output. It is separate from:
If For a useful follow-up, please say whether you are debugging (a) Dokan's kernel driver, (b) the Dokan user-mode library, or (c) your filesystem callbacks, and which capture tool you tried; each has a different output path. |
Uh oh!
There was an error while loading. Please reload this page.
I am trying to debug the driver, but I can't seems to get any debug from the driver, how do I get it?
I am using the latest version
All reactions