Hi ,

I need to get something clarified regarding WinDbg command prompt.

I am using kernel debugging and using a host machine and target
machine for the same.

I have the following problem:

I have connected the host machine and the target machine usng a com
cable and it is working fine. I start WinDbg in my host machine and
then select File -> Kernel Debug. Then it waits for the com1
connection to come alive. I reboot the target machine meanwhile in the
Debug Mode. After the target machine boots up i get the following
messages in command window of WinDbg.

----------------------------------------------------------------------------------------------------------------------------------------

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

Opened \\.\com1
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: C:\WINNT\Symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for ntoskrnl.exe -
Windows XP Kernel Version 2600 UP Free x86 compatible
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
System Uptime: not available
SXS: BasepCreateActCtx() NtOpenFile(\??\C:\??\C:\WINNT
\system32\winlogon.exe) failed
ERROR: DavReadRegistryValues/RegQueryValueExW(4). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(5). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 5
0 - KeepSCMHappyOnStart
24 - KeepSCMHappyOnStart
36 - TellSCMGoodToGo
SavRoam: initializing communications
SavRoam: initializing COM
SavRoam: starting Transman
SavRoam: loading certs from: C:\Program Files\Symantec AntiVirus\
SavRoam: loading ScsComms
SavRoam: communication initialization SUCCEEDED!
watchdog!WdUpdateRecoveryState: Recovery enabled.
----------------------------------------------------------------------------------------------------------------------------------------

The above message shows that kernel debugger connection established.

After this my target machine is completely booted up. Note that i have
not loaded my driver till this point.


The problem is that even after the target machine gets booted, i am
not able to get the command line prompt in the command window. It just
displays Debuggee not connected at the status bar where otherwise
Command Prompt kd> should appear. I don't know if this behaviour is
normal or not.

I need to access the command prompt.

Please help me on the same.

Thanks for any help.

Regards,
Aman.

Can you break into the target OS with Debug->Break (i.e. is the menu option
enabled)?

Sometimes it happened to me that windbg was saying "not connected" after all
those messages, but instead it was connected, and debug->break was working.

Just my two cents
GV

"developer28" <aman.k.sethi@gmail.com> wrote in message
news:1171015640.033050.282900@k78g2000cwa.googlegr oups.com...

HI GV,

Thanks a lot for the help man.
It was the same problem in my case , It was showing not connected but
it breaks into the debugger when i use the menu option break.

Thanks Again.

Aman.