Tell me more ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.

I have debugged drivers on VM (pipe connection) with Windows 7. Now I want to debug a driver in a laptop with Windows 7 (x64) but the WinDbg keeps waiting forever for the connection:

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

Opened \.\com1 Waiting to reconnect...

In the target laptop I boot with this BCD entry:

Identificador           {current}

device                  partition=C:

path                    \windows\system32\winload.exe

description             DebugEntry

locale                  es-ES

inherit                 {bootloadersettings}

recoverysequence        {b3c5a314-b064-11df-ba01-a8d3a819aefa}

recoveryenabled         Yes

bootdebug               Yes

osdevice                partition=C:

systemroot              \windows

resumeobject            {b3c5a312-b064-11df-ba01-a8d3a819aefa}

nx                      OptIn

detecthal               Yes

debug                   Yes

The debug settings on target are:

C:\windows\system32>bcdedit /dbgsettings
debugtype               Serial
debugport               1
baudrate                115200

Baudrate is the same in both host and target because I launch the debugger this way:

windbg.exe -k com:port=COM1,baud=115200

The cable works for kernel debugging because I have used it before, in fact when I monitor the COM1 in the target machine I can see the polling messages comming from the WinDbg and even the Control+Break message... but nothing happens.

The serial port, as expected, is enabled in both BIOS settings.

Also, it seems that Windows is not waiting fot the timeout on COM 1 at boot time, it starts normally without a delay...

Any suggestions?

share|improve this question
1  
Are you sure that your laptop has a "real" COM-port, not a USB-COM or PCMCI-COM? – Sergius Feb 14 at 12:45
Not really, the specs just say "Serial Port". Serial port properties in "Device manager" doesn't help (me) too much. Maybe opening the laptop case? – Julian Feb 14 at 14:36
1  
As an alternative you can use a 1394 port (firewire) for debugging. It works much faster. – Sergius Feb 14 at 19:20

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.