Re : Kernel debugging setup for Windows 2000

NTDEV
1

Hi,

Just forget Windbg if you can then use “c:\Program files\Debugging Tools for Windows\i386kd -v -k port=com_id”

– Sumit

----- Original Message -----
From: Abhijit Mirajkar
To: NT Developers Interest List
Sent: Wed Jul 18 20:44:38 GMT+05:30 2001
Subject: [ntdev] Kernel debugging setup for Windows 2000

Hi All,

I had a strange experience when setting up my Windows 2000 (checked version)
machine for kernel debugging.

As the DDK says (and similar to that for Windows NT), I added the options
‘/debugport=com1 /baudrate=19200’ to the boot.ini
However when I did reboot, the debugger machine didn’t get connected. Same
setup works for NT debugging which is there on the same system.

I was therefore wondering if there is any other way to debug Windows 2000
system.
If any of you know about this or have troubleshooted this before, your
comments will be greatly appreciated.
Thanks,

Regards,
Abhijit

—
You are currently subscribed to ntdev as: xxxxx@elitecore.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

____________________________________________________________
eLitecore Technologies Pvt. Ltd.

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

With the latest windbg at least, windbg will start saying things very
shortly after the target OS comes up. It shouldn’t be necessary to
synch.

Be sure COM1 is enabled in the machine’s BIOS (both sides, of course).
Be sure you can talk from one system to the other via COM1 on the target
and COMx on the debugger system.

–
James Antognini
IBM Watson Research

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com