No debugging logs from win32 applications in vista or seven

[Anonymous]

Hello,
I’ve noticed that there’s a problem, when debugging via virtualkd – no application logs can be seen in windbg. I mean if application is using OutputDebugString() it’s not shown in windbg session. Nevertheless DbgPrint() messages from drivers are shown. I already have “Debug Print filter” set to 0xFFFFFFFF in the registry, so it’s not the issue. And I’ve checked, the logs are shown if you use original \pipecom_1 instead of virtualkd boot entry.

[Hex]

Any chance to fix that?

[support]

Hi,

That’s the default behavior in Windows Vista and later. Please have a look here: http://www.osronline.com/article.cfm?article=295

[Hex]

@bazis wrote:

Hi,

That’s the default behavior in Windows Vista and later.

No it’s not, because, as I’ve written before, I can see all messages in windbg if I switch back to \.pipecom_1.

[support]

Hi,

Fixed in 2.8

[broken850]

restoring to a snapshot of a VirtualBox Win7-x86 machine without VirtualKD, connecting with a serial kernel debugger to com1 on the target — assert works as expected, and it asks whether to Break/Ignore/etc. This is without Service Pack 1, so perhaps it is only the default behavior on SP1?

[Author]

Posts