Niranjan:
A few ideas, as I know this problem can be frustrating. Perhaps you already know this, but, as you say you are new to KD, unless you have a very compelling reason to use COM/NULL, I would strongly consider using 1394. It is much, much faster and not much more difficult to use, especially since you are having trouble with COM.
In any case, I suspect the problem is either that you have no requested an initial breakpoint or, possibly, that you do not have symbols loaded. If either of these is the case, try the following (command lines for both COM and 1394 are included).
TARGET:
BOOT.INI
1394: /debug /debugport=1394 /channel=1 (or /channel=0, et. c.)
COM: No changes
1394: Disable the 1394 controller on the target (using Device Manager, for example).
Reboot.
HOST:
Uninstall WinDbg and reinstall it. Make sure that the folder containing WinDbg.EXE is added to your system path (environment variables on the advanced tab of computer properties). Reboot.
Start WinDbg with the following command line (or connect from in WinDbg with these options).
1394: WinDbg -k 1394:channel=X -b -ysrv*LOCAL_SYMBOL_STORE*http://msdl.microsoft.com/download/symbols
WHERE:
-channel=X -> X is the same chanell number you set in Boot.INI
LOCAL_SYMBOL_STORE is the fullpath of a folder to use a local symbol folder. If you don’t have one or don’t know what this is, it can be any folder on your computer. Just pick one that has nothing else in it.
-OR-
COM: Add -b to your existing command line.
If you still are not seeing output in the command window (WinDbg), try pressing Ctrl+Break or selecting the “Break” item from the “Debug” menu.
I hope this helps. If it does not, and you don’t find the answer elsewhere, please send me the command line you are using for WinDbg.
MM
>> xxxxx@sta.samsung.com 09/14/05 3:28 PM >>>
Hi,
I am a newbie in Kernel mode debugging. I am trying to setup a debug
environment to debug a intermediate driver using a null model cable
connection.
The target system and host system are running windows 2000 professional. I
have configured my target system to start in debug mode by adding the
/debug /debugport=com1 /baudrate=9600 in the boot.ini file. The Host system
is running WinDbg 6.5.0003.7.
When I am enabing kernel mode debugging on com1 port and baudrate=9600, the
windbg shows a message in the connect window “opened \. \com1 waiting
to reconnect” and in the status bar, "debuggee not connected " message.
I have tested the null modem connection between host and target system using
hyperterminal.
Can someone please help me to solve this problem.
Thank you all in advance.
-Niranjan
You are currently subscribed to windbg as: xxxxx@evitechnology.com
To unsubscribe send a blank email to xxxxx@lists.osr.com