Cannot attach kernel debugger RRS feed

  • Question

  • The Driver deploys to the target.  I can install it against a NIC.  It starts successfully using 

    net start drivername

    TOOLS->attach Windows Kernel mode debugger Qualifyer "test"  the name of the target

    Available processes displays only one

    process ID title type username session

    kernel 0 kernel kernel blank 0

    dev system is a I7 MAC running paralleles  and win8 x64

    target is real I5 hardware running win8 release (I don't have a checked build yet)

    But when I attach, it just hangs

    Is there some log I can inspect to see what is going on?

                      Starting New Debugger Session         

    Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Using NET for debugging
    Opened WinSock 2.0
    Waiting to reconnect...
    XXXXXXXXX42AA\XXXXXXX (npipe WinIDE_01CE09544640B000) connected at Tue Feb 12 12:08:00 2013

    computername username editied to XXX for post, but they are valid

    11:21:13:937]: Install Driver Test Components summary:

    [11:21:13:937]:   Installing .NET Framework (possible reboot): Pass
    Initialize: Computer: 
    [11:21:13:937]:   Installing test automation (x86): Pass
    [11:21:13:937]:   Installing test automation (x64): Pass
    [11:21:13:937]:   Installing debuggers (x86): Pass
    [11:21:13:937]:   Installing debuggers (x64): Pass
    [11:21:13:937]:   Installing driver test framework: Pass
    [11:21:13:937]:   Installing automatic failure injection tools: Pass
    [11:21:13:937]:   Registering logging components: Pass
    [11:21:13:937]:   Configure debugger settings (x64) (possible reboot): Pass
    [11:21:13:937]:   Configure computer settings (x64) (possible reboot): Pass
    [11:21:13:937]:   Creating system restore point: Pass
    Result Group Completed: Pass
    Initialize: Computer: 
    Initialize: Computer: 
    Initialize: Computer: 
    Progress event: Current: 19, Max: 19, Message: ""

    Tuesday, February 12, 2013 7:11 PM

All replies

  • When you say that it hangs, do you mean that your Visual Studio instance on your host machine hangs, or your entire host machine hangs, or your target machine hangs?

    I'm guessing you mean that VS hangs. Do you even see the remote debugging window (that should tell you it is waiting to connect)? Or it just hangs at the "Attach to process" window?

    Which configuration did you use for remote debugging (network, serial, other? Any hand-picked bus parameters, or did you use the default settings) ? Are you able to debug using the command line and WinDbg?

    I'm guessing that the log you attached is the one from the remote computer configuration? If so, it does look like the remote machine was properly configured.

    Max -- This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, February 12, 2013 10:58 PM
  • I am switching to a checked build of Win 8 x64 on the target.

    The Dev machine VS 2012 Pro hangs when attempting to connect.  We will see if a checked target works better.

    Wednesday, February 13, 2013 5:24 PM
  • It should have no difference.  The checked build of the OS gives you a number debugging check but the actual link for debugging is the same, so there will be no difference unless you have done something that messed up the test environment and replacing the OS fixes it.

    I can't say what is failing, but the OS will not impact it.  Step back and check all the procedures and troublshooting from

    Don Burn Windows Filesystem and Driver Consulting Website: Blog:

    Wednesday, February 13, 2013 5:57 PM