Windbg always show "Waiting to reconnect..."

Question

Windbg always show "Waiting to reconnect..."

Dear all,

I want to debug win7 OS login issue.

I had two machines, one is the Host, and the other is the target system(win7 OS).

The two machines was connected by serial port.

I had set below command on the target machine.

Target:

bcdedit /debug on

• bcdedit /dbgsettings serial debugport:1 baudrate:115200

Host:

Open windbg tool, and select kernal debug.

The tool always show "Waiting to reconnect..."

Is there any problem for the steps?

Thanks. 

Answer 1

Have you reboot your target machine.

Then start into debug mode only.

regards

matt

Answer 2

Dear Matt,

I had already reboot the target machine, but it still cannot connect.

Answer 3

Have you

"Turn on file and printer sharing"

and both the machine are into same workgroup.

regard

matt

Answer 4

Dear Matt,

What does the "Turn on file and printer sharing" mean?

How could I turn on the function "Turn on file and printer sharing"?

Thanks.

After checked, the item"Turn on file and printer sharing" had already turn on, and the two machines are in the same group.

Answer 5

I had the same problem while debugging a virtual machine. I don't know if it's the same here but I unblocked it by Ctrl+Break (or Debug->Break with the menu).

Answer 6

Setting Up the Target Computer

 

In an elevated Command Prompt window, enter:

 

1. bcdedit /debug on

The operation completed successfully

 

1. bcdedit /dbgsettings serial debugport:2 baudrate:115200

        The operation completed successfully

Note  The baud rate must be the same on the host computer and target computer.

 

1. bcdedit /enum all

display all boot settings on the system like

 

. . . . . .

. . . . . .

. . . . . .

 

Windows Boot Loader ------------------- identifier                                 {current} device partition=C: path \Windows\system32\winload.exe description              Windows 7 Debug locale en-US inherit {bootloadersettings} recoverysequence {bb193046-0fba-11e1-8882-fcacd893597b} debugtype               Serial debugport               2 baudrate                                 115200 recoveryenabled Yes osdevice partition=C: systemroot \Windows resumeobject {bb193044-0fba-11e1-8882-fcacd893597b} nx OptIn debug                      Yes

. . . . . .

. . . . . .

. . . . . .

 

1. bcdedit /copy {current} /d DebugEntry

If success then BCDEdit would display like this result

The entry was successfully copied to { bb193044-0fba-11e1-8882-fcacd893597b }

 

The global universal identifier (GUID) that appears between braces in the preceding message is the identifier of the new boot entry. You use the identifier to represent the entry in all subsequent BCDEdit commands.

 

1. bcdedit /displayorder {current} { bb193044-0fba-11e1-8882-fcacd893597b }

don’t copy this GUID, use your system GUID

 

1. bcdedit

verify that the display order is correct

. . . . . .

. . . . . .

. . . . . .

Windows Boot Manager -------------------- identifier                                 {bootmgr} device partition       =\Device\HarddiskVolume3 description              Windows Boot Manager locale                      en-US inherit                     {globalsettings} default                    {default} resumeobject          {bb193044-0fba-11e1-8882-fcacd893597b} displayorder            {current} toolsdisplayorder    {memdiag} timeout                   30

. . . . . .

. . . . . .

. . . . . .

Windows Boot Manager entry also includes the boot menu display order

 

1. bcdedit /enum osloader

 

. . . . . .

. . . . . .

. . . . . .

Windows Boot Loader -------------------- identifier                                 {bb193044-0fba-11e1-8882-fcacd893597b} device partition       =\Device\HarddiskVolume3 description              DebugEntry locale                      en-US inherit                     {globalsettings} default                    {default} resumeobject          {bb193044-0fba-11e1-8882-fcacd893597b} displayorder            {current} toolsdisplayorder    {memdiag} debug                      Yes

. . . . . .

. . . . . .

. . . . . .

 

1. bcdedit /debug {bb193044-0fba-11e1-8882-fcacd893597b} on

The operation completed successfully

 

                                . . . . . .

. . . . . .

. . . . . .

Windows Boot Loader -------------------- identifier                                 {bb193044-0fba-11e1-8882-fcacd893597b} device partition       =\Device\HarddiskVolume3 description              DebugEntry locale                      en-US inherit                     {globalsettings} default                    {default} resumeobject          {bb193044-0fba-11e1-8882-fcacd893597b} displayorder            {current} toolsdisplayorder    {memdiag} debug                      Yes

. . . . . .

. . . . . .

. . . . . .

Check boot entry named DebugEntry and a Kernel debugger attribute on the entry with a value of Yes

 

1. bcdedit /default {bb193044-0fba-11e1-8882-fcacd893597b}

The operation completed successfully

 

Again do bcdedit to cross verify all parameters like

description              DebugEntry debug                      Yes

identifier                                 {bb193044-0fba-11e1-8882-fcacd893597b}

1. Reboot the target computer.

 

Two options will be there

Microsoft Windows

DebugEntry                             choose this one

Answer 7

Setting Up the Target Computer

 

In an elevated Command Prompt window, enter:

 

1. bcdedit /debug on

The operation completed successfully

 

1. bcdedit /dbgsettings serial debugport:2 baudrate:115200

        The operation completed successfully

Note  The baud rate must be the same on the host computer and target computer.

 

1. bcdedit /enum all

display all boot settings on the system like

 

. . . . . .

. . . . . .

. . . . . .

 

Windows Boot Loader ------------------- identifier                                 {current} device partition=C: path \Windows\system32\winload.exe description              Windows 7 Debug locale en-US inherit {bootloadersettings} recoverysequence {bb193046-0fba-11e1-8882-fcacd893597b} debugtype               Serial debugport               2 baudrate                                 115200 recoveryenabled Yes osdevice partition=C: systemroot \Windows resumeobject {bb193044-0fba-11e1-8882-fcacd893597b} nx OptIn debug                      Yes

. . . . . .

. . . . . .

. . . . . .

 

1. bcdedit /copy {current} /d DebugEntry

If success then BCDEdit would display like this result

The entry was successfully copied to { bb193044-0fba-11e1-8882-fcacd893597b }

 

The global universal identifier (GUID) that appears between braces in the preceding message is the identifier of the new boot entry. You use the identifier to represent the entry in all subsequent BCDEdit commands.

 

1. bcdedit /displayorder {current} { bb193044-0fba-11e1-8882-fcacd893597b }

don’t copy this GUID, use your system GUID

 

1. bcdedit

verify that the display order is correct

. . . . . .

. . . . . .

. . . . . .

Windows Boot Manager -------------------- identifier                                 {bootmgr} device partition       =\Device\HarddiskVolume3 description              Windows Boot Manager locale                      en-US inherit                     {globalsettings} default                    {default} resumeobject          {bb193044-0fba-11e1-8882-fcacd893597b} displayorder            {current} toolsdisplayorder    {memdiag} timeout                   30

. . . . . .

. . . . . .

. . . . . .

Windows Boot Manager entry also includes the boot menu display order

 

1. bcdedit /enum osloader

 

. . . . . .

. . . . . .

. . . . . .

Windows Boot Loader -------------------- identifier                                 {bb193044-0fba-11e1-8882-fcacd893597b} device partition       =\Device\HarddiskVolume3 description              DebugEntry locale                      en-US inherit                     {globalsettings} default                    {default} resumeobject          {bb193044-0fba-11e1-8882-fcacd893597b} displayorder            {current} toolsdisplayorder    {memdiag} debug                      Yes

. . . . . .

. . . . . .

. . . . . .

 

1. bcdedit /debug {bb193044-0fba-11e1-8882-fcacd893597b} on

The operation completed successfully

 

                                . . . . . .

. . . . . .

. . . . . .

Windows Boot Loader -------------------- identifier                                 {bb193044-0fba-11e1-8882-fcacd893597b} device partition       =\Device\HarddiskVolume3 description              DebugEntry locale                      en-US inherit                     {globalsettings} default                    {default} resumeobject          {bb193044-0fba-11e1-8882-fcacd893597b} displayorder            {current} toolsdisplayorder    {memdiag} debug                      Yes

. . . . . .

. . . . . .

. . . . . .

Check boot entry named DebugEntry and a Kernel debugger attribute on the entry with a value of Yes

 

1. bcdedit /default {bb193044-0fba-11e1-8882-fcacd893597b}

The operation completed successfully

 

Again do bcdedit to cross verify all parameters like

description              DebugEntry debug                      Yes

identifier                                 {bb193044-0fba-11e1-8882-fcacd893597b}

1. Reboot the target computer.

 

Two options will be there

Microsoft Windows

DebugEntry                             choose this one

Answer 8

I had verified above steps, but the windbg still show "Waiting to reconnect..." .

It seems not working.

I really don't know why.

Answer 9

Okay, if all the above steps are really verified and correct as per you.

Then only two things are stranded over here.

1. Might be your host WinDbg settings are not proper?

2. Either your host or target don't have either proper serial port driver or hardware.

Go to device manager and check; is the serial port i.e Ports (COM & LPT) is okay means not showing any yellow mark.

Last check your NULL modem cable using the hyper terminal on the Host and Target machines, does it works perfectly?

Verify that  hardware is functional and you are indeed able to connect Host to Target?

Actually, the NULL modem cable is critical since it switches RX to TX, as well as the physical routing of RTX/CTS and DCD/DSR/DTR.

Suggestion:

Serial debug is slow so if possible switch to

1394/ USB debug cable/ VM

all depends on your requirements also

regards

matt

Answer 10

Hi,

May be you are missing registry entry. You need to follow below settings

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Debug Print Filter and add the following value "DEFAULT" : REG_DWORD : 0xFFFFFFFF and then reboot

if Debug Print Filter is not there, then you have to create new.

Regards,

Muthu

Answer 11

All listed above does not work. I find solution which help me:

Windbg is not the same as visual studio remote debugger which you run first as a server heaving an tcp socket to which you plug the GDI debuggers as a client.

You must run windbg first and load the system being debugging after that.

If You use virtual machine, power on the machine first to make the virtual COM&pipe, connect your debugger to the named pipe, and only then load the VM OS.

Solution #2: reboot PC being debugging, it connect to the debugger at the boot-time, ony at the boot-time.

Answer 12

Actually you can run the system and break in.   WinDBG has the ability to break into a running system, and then a .reload will synchronize the symbols.   Have you checked that the link between the two systems is functioning correctly?   If this is truly a serial link then fire up a terminal emulation program on each system and see if they talk over the link.   Common problems for a serial link are getting a straight through versus null modem style cable, or that the because of many reasons the cable does not work correctly for 115200 baud.   For that matter be sure the baudrate is the same on both Windbg and the boot settings of the test system.

For the responses above, nothing about File and Print sharing will impact Windbg.   Also, while the registry setting impacts debug output, it does not impact the connection to Windbg.

---

Don Burn Windows Driver Consulting Website: http://www.windrvr.com