Request support for windows kernel log messages

[x64bugreport]

Request support for windows kernel log messages

[janwilmans]

I don't know how to implement it, but you are welcome to make a pull request, even if it's just a demonstration of how it's done.

[593749519]

If kernel debug info is provided, it'll be the best debug view ever! To do it on windows vista above, need write a windows driver and call DbgSetDebugPrintCallback to set a callback function to record the debug info. the driver should be signed by Microsoft

[janwilmans]

I have no idea how to do this, but I would help integrate it if someone takes point? Jan

…

On Thu, Jul 17, 2025, 15:35 593749519 ***@***.***> wrote: *593749519* left a comment (CobaltFusion/DebugViewPP#404) <#404 (comment)> to do it on windows vista above, need write a windows driver and call DbgSetDebugPrintCallback to set a callback function to record the debug info. the driver should be signed by Microsoft — Reply to this email directly, view it on GitHub <#404 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNITBEPMEP43QCULXZM3CD3I6RDFAVCNFSM6AAAAACBTXCXSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOBUGEYDANRRGY> . You are receiving this because you commented.Message ID: ***@***.***>

[593749519]

Besides write a new driver, I digged into sysinternals debugview and reversed its driver interface. If you are interested, see https://github.com/593749519/DebugView-interface-reversed

[x64bugreport]

I don't know how to implement it, but you are welcome to make a pull request, even if it's just a demonstration of how it's done.

I am not sure whether it is in compliance with the rules to reuse the Microsoft debugview driver, but I think you can refer to the driver communication method provided by 593749519 to call the Microsoft debugview driver to complete these functions. The UI experience of Microsoft debugview is really terrible. In comparison, the UI of debugviewpp is simply great. If it can cover the Microsoft debugview function, it can perfectly replace it.

[x64bugreport]

Besides write a new driver, I digged into sysinternals debugview and reversed its driver interface. If you are interested, see https://github.com/593749519/DebugView-interface-reversed

Thank you very much for providing the debugview driver communication code

[janwilmans]

I don't think even the original DbgView kernel driver works on Vista and above? I will go look at the reversed driver!
@x64bugreport and @593749519 sounds like you both have test-scenarios that I could use to see if its working? Could you provide them?

[janwilmans]

Btw have you tried:

• put dbgview.exe (the original) in the executable directory of DebugView.exe
• click Log->Connect Debugview Agent

This is a feature that starts dbgview in 'agent mode', it was intended to run on a different machine, and connect to it via a socket, but some time again I reversed the socket messages and I think I should be able to capture kernel message also ?

I never had a proper test scenario for it, so I would be grateful with any help you can provide testing this

[janwilmans]

And there is actually another really useful feature I would like to borrow from dbgview: passthrough mode.
in passthrough mode, dbgview captures messages, but a debugger that is attached to the program will ALSO receive the message, right now, that is not possible with Debugview.

[x64bugreport]

And there is actually another really useful feature I would like to borrow from dbgview: passthrough mode. in passthrough mode, dbgview captures messages, but a debugger that is attached to the program will ALSO receive the message, right now, that is not possible with Debugview.

I hope that I don't need to rely on debugview agent to transfer logs. I hope debugviewpp can directly support it and replace Microsoft's terrible debugview ui.