No debugging logs from win32 applications in vista or seven

Sysprogs forums › Forums › VisualDDK/VirtualKD discussion › No debugging logs from win32 applications in vista or seven

  • This topic has 5 replies, 4 voices, and was last updated 12 years ago by Hex.
Log In Register Lost Password
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • April 24, 2012 at 10:18 #482
    Anonymous
    Participant

    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.

    May 14, 2012 at 07:58 #2212
    Hex
    Participant

    Any chance to fix that?

    July 8, 2012 at 12:29 #2214
    support
    Keymaster

    Hi,

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

    August 29, 2012 at 05:44 #2216
    Hex
    Participant

    @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.

    August 30, 2012 at 20:49 #2215
    support
    Keymaster

    Hi,

    Fixed in 2.8

    November 5, 2012 at 05:22 #2213
    broken850
    Participant

    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
Log In Register Lost Password
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.