Hi everyone!
Can anybody give me an advice regarding the win2k kernel debugging? My driver hangs at initialization state and I cannot enter into debug mode to track the bug out. I’ve created second string in the target system’s boot.ini file: multi(0)disk(0)rdisk(0)partition(1)\WINNT=“Microsoft Windows 2000 Debug Mode” /fastdetect /debugport=com1 /baudrate=115200
Then I started windbg, tried to connect to remote session and nothing happened.
What shoul I do to debug driver initialization routine, where should I place symbols and sources for my driver and how can I set the breakpoints to driver routines. I would be very grateful for any comprehensive answer.
/regards/
Check connection by using hyper terminal between host and target via com
port. does it work?
If doesnt work, check com configuration at first.
Kimi
-----Original Message-----
From: Andrew Sloven [mailto:xxxxx@amurshipyard.ru]
Sent: Thursday, September 19, 2002 9:12 AM
To: NT Developers Interest List
Subject: [ntdev] Kernel debugging
Hi everyone!
Can anybody give me an advice regarding the win2k kernel debugging? My
driver hangs at initialization state and I cannot enter into debug mode to
track the bug out. I’ve created second string in the target system’s
boot.ini file: multi(0)disk(0)rdisk(0)partition(1)\WINNT=“Microsoft Windows
2000 Debug Mode” /fastdetect /debugport=com1 /baudrate=115200
Then I started windbg, tried to connect to remote session and nothing
happened.
What shoul I do to debug driver initialization routine, where should I place
symbols and sources for my driver and how can I set the breakpoints to
driver routines. I would be very grateful for any comprehensive answer.
/regards/
You are currently subscribed to ntdev as: xxxxx@citrix.co.jp
To unsubscribe send a blank email to %%email.unsub%%
Hi,
You can try to add /crashdebug option in boot.ini
Thanks,
Futoshi
-----Original Message-----
From: Andrew Sloven [mailto:xxxxx@amurshipyard.ru]
Sent: Thursday, September 19, 2002 9:12 AM
To: NT Developers Interest List
Subject: [ntdev] Kernel debugging
Hi everyone!
Can anybody give me an advice regarding the win2k kernel debugging? My
driver hangs at initialization state and I cannot enter into debug mode to
track the bug out. I’ve created second string in the target system’s
boot.ini file: multi(0)disk(0)rdisk(0)partition(1)\WINNT=“Microsoft Windows
2000 Debug Mode” /fastdetect /debugport=com1 /baudrate=115200
Then I started windbg, tried to connect to remote session and nothing
happened.
What shoul I do to debug driver initialization routine, where should I place
symbols and sources for my driver and how can I set the breakpoints to
driver routines. I would be very grateful for any comprehensive answer.
/regards/
You are currently subscribed to ntdev as: xxxxx@citrix.co.jp
To unsubscribe send a blank email to %%email.unsub%%
Looks like you forgot /Debug …
-Jeff
-----Original Message-----
From: Andrew Sloven [mailto:xxxxx@amurshipyard.ru]
Sent: Wednesday, September 18, 2002 8:12 PM
To: NT Developers Interest List
Subject: [ntdev] Kernel debugging
Hi everyone!
Can anybody give me an advice regarding the win2k kernel debugging? My
driver hangs at initialization state and I cannot enter into debug mode to
track the bug out. I’ve created second string in the target system’s
boot.ini file: multi(0)disk(0)rdisk(0)partition(1)\WINNT=“Microsoft Windows
2000 Debug Mode” /fastdetect /debugport=com1 /baudrate=115200
Then I started windbg, tried to connect to remote session and nothing
happened.
What shoul I do to debug driver initialization routine, where should I place
symbols and sources for my driver and how can I set the breakpoints to
driver routines. I would be very grateful for any comprehensive answer.
/regards/
You are currently subscribed to ntdev as: xxxxx@concord.com
To unsubscribe send a blank email to %%email.unsub%%
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
the latest virus scan software available for the presence of computer
viruses.
**********************************************************************