windbg attachment

WINDBG
1

I am trying to setup to debug a driver on a w2k system. I have a checked
version of w2k on my target machine and a free version of w2k on my host
machine. I know that the cable between the two machines work by using
HyperTerminal. I start windbg with it setup to do kernel debugging and
using com1 at 19200. I do a ‘g’ in windbg and it indicates that it is
waiting for a connection. I have the boot.ini on the target setup to use
com1 and a baudrate of 19200. I boot up the target and it stops the boot
during the loading of drivers. I don’t get any messages on the windbg
screen. If a do a ctrl C in windbg it indicates that it has sent a break
message but it never completes the connection. If I allow the target to
boot all the way up without having windbg running on the host, the target
boots all the way up. Then if I bring up windbg and do a ctrl C it again
indicates it has sent a break message and the target machine freezes (i.e.
the mouse does not move). But it still cannot do a complete connection.

Does anyone have any idea what I may be doing wrong? I have poured over
the DDK documentation and the only thing I can see is that I am not
setting
up the symbols on the host. I am not sure where to get the symbols. I
loaded down the ddk from the Microsoft site. Do I need to have the
symbols
loaded on my host?

Thanks
Dave Stallmo

2

Its possible that a break point is set and you can just press F5 or do
“g” to continue running and it should boot the target machine.

-----Original Message-----
From: xxxxx@borg3.com [mailto:xxxxx@borg3.com]
Sent: Thursday, May 30, 2002 10:37 AM
To: Kernel Debugging Interest List
Subject: [windbg] windbg attachment

I am trying to setup to debug a driver on a w2k system. I have a checked
version of w2k on my target machine and a free version of w2k on my host
machine. I know that the cable between the two machines work by using
HyperTerminal. I start windbg with it setup to do kernel debugging and
using com1 at 19200. I do a ‘g’ in windbg and it indicates that it is
waiting for a connection. I have the boot.ini on the target setup to use
com1 and a baudrate of 19200. I boot up the target and it stops the boot
during the loading of drivers. I don’t get any messages on the windbg
screen. If a do a ctrl C in windbg it indicates that it has sent a break
message but it never completes the connection. If I allow the target to
boot all the way up without having windbg running on the host, the target
boots all the way up. Then if I bring up windbg and do a ctrl C it again
indicates it has sent a break message and the target machine freezes (i.e.
the mouse does not move). But it still cannot do a complete connection.

Does anyone have any idea what I may be doing wrong? I have poured over
the DDK documentation and the only thing I can see is that I am not
setting
up the symbols on the host. I am not sure where to get the symbols. I
loaded down the ddk from the Microsoft site. Do I need to have the
symbols
loaded on my host?

Thanks
Dave Stallmo

You are currently subscribed to windbg as: xxxxx@synaptics.com
To unsubscribe send a blank email to %%email.unsub%%

3

What version of WinDbg are you using? Go for the newest.

When you do this:

Then if I bring up windbg and do a ctrl C it again
indicates it has sent a break message and the target machine freezes (i.e.
the mouse does not move). But it still cannot do a complete connection.

can you type in commands like ‘g’? It is normal for the target machine to
“lock” when you break. When you do a ctrl-c you are breaking the execution
of the OS so nothing is really running except the necessary debugging stuff.
Make sense?

Hope this helps, Chris

4

Hi all,

I would like to specify someone(Process/Thread) who will be able to create
the file during winlogon.exe.
First of All, I tried to confirm how many time IRP_MJ_CREATE will be sent
during logon process from staring GINA by using FileMon.exe
I knew it was 661.
Next I set the break point such as “bp nt!NtCreateFile 661” on windbg during
live debugging. but I could not break there. after all windbg did not stop
at any point.

What should I do a kind of thing? Does anyone have any good idea?

Thanks,
Futoshi