Debuggee not connected, bp not supported

OSR_Community_User · October 5, 2010, 1:55pm

I have a basic question.

I have compiled not even developed) a very simple kernel driver.

It installs, leaves some trace in a file I write to.

But when I try to you WinDbg to trace it, to see the result of DbgPrint I firt see this :

Debuggee not connected

Not knowing what to connect, I decided to go into Kernel Debug.

Symbols load. I tried to do a “bp”, it says it is not supported by the current debuggee (which I can understand).

No print out from DbgPrint appears above the cmd prompt of Windbg although the file to which the driver also writes is getting updated.

What must I do? How do I specify that I want to trace a given driver I loaded and is running?

Connected to Windows XP 2600 x86 compatible target at (Tue Oct 5 13:44:14.015 2010 (UTC - 4:00)), ptr64 FALSE
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
*******************************************************************************
WARNING: Local kernel debugging requires booting with kernel
debugging support (/debug or bcdedit -debug on) to work optimally.
*******************************************************************************
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.100427-1636
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Oct 5 13:44:15.015 2010 (UTC - 4:00)
System Uptime: 0 days 0:54:11.697
lkd> .reload
Connected to Windows XP 2600 x86 compatible target at (Tue Oct 5 13:45:12.828 2010 (UTC - 4:00)), ptr64 FALSE
Loading Kernel Symbols
…
…
Loading User Symbols
…
Loading unloaded module list
…
lkd> bp
^ Operation not supported by current debuggee error in ‘bp’

mm1 · October 5, 2010, 1:58pm

You need to a two machine kd setup; local kernel debugging won’t support
what you are trying to do.

So, you either need a second machine and either a 1394 or serial cable, or
either VMWare of VirtualPC.

Good luck,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Tuesday, October 05, 2010 1:53 PM
To: Kernel Debugging Interest List
Subject: [windbg] Debuggee not connected, bp not supported

I have a basic question.

I have compiled not even developed) a very simple kernel driver.

It installs, leaves some trace in a file I write to.

But when I try to you WinDbg to trace it, to see the result of DbgPrint I
firt see this :

Debuggee not connected

Not knowing what to connect, I decided to go into Kernel Debug.

Symbols load. I tried to do a “bp”, it says it is not supported by the
current debuggee (which I can understand).

No print out from DbgPrint appears above the cmd prompt of Windbg although
the file to which the driver also writes is getting updated.

What must I do? How do I specify that I want to trace a given driver I
loaded and is running?

Connected to Windows XP 2600 x86 compatible target at (Tue Oct 5
13:44:14.015 2010 (UTC - 4:00)), ptr64 FALSE
Symbol search path is:
srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
****************************************************************************
***
WARNING: Local kernel debugging requires booting with kernel
debugging support (/debug or bcdedit -debug on) to work optimally.
****************************************************************************
***
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.100427-1636
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Oct 5 13:44:15.015 2010 (UTC - 4:00)
System Uptime: 0 days 0:54:11.697
lkd> .reload
Connected to Windows XP 2600 x86 compatible target at (Tue Oct 5
13:45:12.828 2010 (UTC - 4:00)), ptr64 FALSE
Loading Kernel Symbols
…
…
Loading User Symbols
…
Loading unloaded module list
…
lkd> bp
^ Operation not supported by current debuggee error in ‘bp’

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

OSR_Community_User · October 5, 2010, 2:01pm

That message about “Local debugging” is suspicious; it sounds like you are
trying to debug the same system you are running on. This is not going to
work. In particular, if you take a breakpoint in the kernel, how are you
going to see what has happened? (Since the kernel has stopped, how is
WinDbg actually going to run?) Use a two-machine debugging model (one of
them can be a VM)
joe

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Tuesday, October 05, 2010 1:53 PM
To: Kernel Debugging Interest List
Subject: [windbg] Debuggee not connected, bp not supported

I have a basic question.

I have compiled not even developed) a very simple kernel driver.

It installs, leaves some trace in a file I write to.

But when I try to you WinDbg to trace it, to see the result of DbgPrint I
firt see this :

Debuggee not connected

Not knowing what to connect, I decided to go into Kernel Debug.

Symbols load. I tried to do a “bp”, it says it is not supported by the
current debuggee (which I can understand).

No print out from DbgPrint appears above the cmd prompt of Windbg although
the file to which the driver also writes is getting updated.

What must I do? How do I specify that I want to trace a given driver I
loaded and is running?

Connected to Windows XP 2600 x86 compatible target at (Tue Oct 5
13:44:14.015 2010 (UTC - 4:00)), ptr64 FALSE
Symbol search path is:
srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
****************************************************************************
***
WARNING: Local kernel debugging requires booting with kernel
debugging support (/debug or bcdedit -debug on) to work optimally.
****************************************************************************
***
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.100427-1636
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Oct 5 13:44:15.015 2010 (UTC - 4:00)
System Uptime: 0 days 0:54:11.697
lkd> .reload
Connected to Windows XP 2600 x86 compatible target at (Tue Oct 5
13:45:12.828 2010 (UTC - 4:00)), ptr64 FALSE
Loading Kernel Symbols
…
…
Loading User Symbols
…
Loading unloaded module list
…
lkd> bp
^ Operation not supported by current debuggee error in ‘bp’

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

–
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

OSR_Community_User · October 5, 2010, 2:11pm

Yes, I thought about that. But remote debugging does not seem to help…

I then get on the server :

VISTABOX\Frank (tcp 192.168.0.101:49419) connected at Tue Oct 05 14:08:43 2010
[VISTABOX\Frank (tcp 192.168.0.101:49419)] lkd> bp
^ Operation not supported by current debuggee error in ‘bp’

Can’t I say which driver to look at? How can I look at its DbgPrint?

mm1 · October 5, 2010, 2:14pm

That’s remote debugging, not kernel debugging.

You need to setup kd using either two machines and a 1394 or null modem
cable (strictly speaking, a special usb cable will work) or use VMWare or
VirtualPC.

Good luck,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Tuesday, October 05, 2010 2:10 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Debuggee not connected, bp not supported

Yes, I thought about that. But remote debugging does not seem to help…

I then get on the server :

VISTABOX\Frank (tcp 192.168.0.101:49419) connected at Tue Oct 05 14:08:43
2010
[VISTABOX\Frank (tcp 192.168.0.101:49419)] lkd> bp
^ Operation not supported by current debuggee error in ‘bp’

Can’t I say which driver to look at? How can I look at its DbgPrint?

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Tim_Roberts · October 5, 2010, 2:20pm

xxxxx@gmail.com wrote:

I have a basic question.

I have compiled not even developed) a very simple kernel driver.

It installs, leaves some trace in a file I write to.

But when I try to you WinDbg to trace it, to see the result of DbgPrint I firt see this :

Debuggee not connected
…
What must I do? How do I specify that I want to trace a given driver I loaded and is running?

If you just want to watch the debug print output, and you don’t really
need to set breakpoints yet, you can use the DebugView utility from
SysInternals. I think I can honestly say there is no tool I rely on
more than DebugView.

http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

OSR_Community_User · October 5, 2010, 2:37pm

mm wrote:

"That’s remote debugging, not kernel debugging. You need to setup kd using either two machines and a 1394 or null modem cable (strictly speaking, a special usb cable will work) or use VMWare or VirtualPC. "

I am lost.

I would need a special cable? IP is not good enough?
I can use neither local debugging nor remote debugging facilities to see the debug messages of my kernel driver? (Never mind at this stage the bp).

mm1 · October 5, 2010, 2:41pm

If all you want to do is see traces, then I’d suggest using DbgView.

If you actually need to do anything remotely related to ‘debugging’ - i. e.
breakpoints, et. c. - then, yes, you will need to setup windbg as I
described earlier.

You might want to read the ‘kernel_debugging_tutorial.doc’ in the root of
your windbg installation.

Good luck,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Tuesday, October 05, 2010 2:35 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Debuggee not connected, bp not supported

mm wrote:

"That’s remote debugging, not kernel debugging. You need to setup kd using
either two machines and a 1394 or null modem cable (strictly speaking, a
special usb cable will work) or use VMWare or VirtualPC. "

I am lost.

I would need a special cable? IP is not good enough?
I can use neither local debugging nor remote debugging facilities to see
the debug messages of my kernel driver? (Never mind at this stage the bp).

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Paul_Sanders-1 · October 5, 2010, 2:41pm

Read the first quarter of the help file. It will take about an hour, but all your questions will be answered. No IP, serial debug cable, 1394 or VM are your only options to debug. It’s actually easy, but read the first part of the help file.

Paul
----- Original Message -----
From: “delplanque francoise”
To: “Kernel Debugging Interest List”
Sent: Tuesday, October 5, 2010 2:34:51 PM
Subject: RE:[windbg] Debuggee not connected, bp not supported

mm wrote:

"That’s remote debugging, not kernel debugging. You need to setup kd using either two machines and a 1394 or null modem cable (strictly speaking, a special usb cable will work) or use VMWare or VirtualPC. "

I am lost.

1) I would need a special cable? IP is not good enough?

2) I can use neither local debugging nor remote debugging facilities to see the debug messages of my kernel driver? (Never mind at this stage the bp).

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Jen-Lung_Chiu · October 5, 2010, 2:41pm

Please check http://msdn.microsoft.com/en-us/library/ff551898(v=VS.85).aspx how to setup kernel debugging. Thanks,

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Tuesday, October 05, 2010 11:35 AM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Debuggee not connected, bp not supported

mm wrote:

"That’s remote debugging, not kernel debugging. You need to setup kd using either two machines and a 1394 or null modem cable (strictly speaking, a special usb cable will work) or use VMWare or VirtualPC. "

I am lost.

I would need a special cable? IP is not good enough?
I can use neither local debugging nor remote debugging facilities to see the debug messages of my kernel driver? (Never mind at this stage the bp).

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Paul_Sanders-1 · October 5, 2010, 2:42pm

and this, too, ‘kernel_debugging_tutorial.doc’

Doesn’t take long to read these.
----- Original Message -----
From: “Paul Sanders”
To: “Kernel Debugging Interest List”
Sent: Tuesday, October 5, 2010 2:40:44 PM
Subject: Re: [windbg] Debuggee not connected, bp not supported

Read the first quarter of the help file. It will take about an hour, but all your questions will be answered. No IP, serial debug cable, 1394 or VM are your only options to debug. It’s actually easy, but read the first part of the help file.

Paul
----- Original Message -----
From: “delplanque francoise”
To: “Kernel Debugging Interest List”
Sent: Tuesday, October 5, 2010 2:34:51 PM
Subject: RE:[windbg] Debuggee not connected, bp not supported

mm wrote:

"That’s remote debugging, not kernel debugging. You need to setup kd using either two machines and a 1394 or null modem cable (strictly speaking, a special usb cable will work) or use VMWare or VirtualPC. "

I am lost.

1) I would need a special cable? IP is not good enough?

2) I can use neither local debugging nor remote debugging facilities to see the debug messages of my kernel driver? (Never mind at this stage the bp).

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Tim_Roberts · October 5, 2010, 2:46pm

xxxxx@gmail.com wrote:

"That’s remote debugging, not kernel debugging. You need to setup kd using either two machines and a 1394 or null modem cable (strictly speaking, a special usb cable will work) or use VMWare or VirtualPC. "

I am lost.

I would need a special cable? IP is not good enough?

That is correct. The kernel debugger is at the very heart of the
operating system. In order for it to debug the operating system and its
drivers, it has to live apart from the system and its drivers. It
cannot use the network stack. Otherwise, how could you debug a network
driver? Instead, the debugger talks directly to either serial port
hardware or 1394 hardware, bypassing the normal drivers.

I can use neither local debugging nor remote debugging facilities to see the debug messages of my kernel driver? (Never mind at this stage the bp).

DebugView is the answer here.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

OSR_Community_User · October 5, 2010, 2:54pm

Tim,

Thank you for your DebugView suggestion, installed, rebooted, works like a charm.

As far as this 1394 cable is concerned. How do I ascertian my two boxes can handle such connections?

I only see USB ports and the few of the internet cable kind.

mm1 · October 5, 2010, 2:57pm

It’s quite possible that your machines might not have 1394 ports; lots
don’t. However, they are easy to get, though you have to be careful which
chipset is used - TI Chipsets work best.

Any easy way to ensure that your 1394 cards work with windbg is to get them
from osronline.com:

https://www.osronline.com/custom.cfm?name=index_fullframeset.cfm&pageURL=htt
ps://www.osronline.com/store/index.cfm

Good luck,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Tuesday, October 05, 2010 2:52 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Debuggee not connected, bp not supported

Tim,

Thank you for your DebugView suggestion, installed, rebooted, works like a
charm.

As far as this 1394 cable is concerned. How do I ascertian my two boxes can
handle such connections?

I only see USB ports and the few of the internet cable kind.

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

OSR_Community_User · October 5, 2010, 3:25pm

Paul,

Thank you for your suggestion. I will read the tutorial.

" No IP, serial debug cable, 1394 or VM are your only options to debug."

The first thing I noticed in the debugging kernel tutorial you mentioned, is that when it shows the kernel debugging dialog, it only has tabs for COM, 1394 and Local. While I have tabs for USB 2.0 and NET.

I think mm mentioned something about USB cables (that I have a lot of), can’t they be used? Must they be “special” and in what way?

OSR_Community_User · October 5, 2010, 3:31pm

Okay, I see in the WInDbg info about the special USB 2.0 cable. Thank you for your collective help.

mm1 · October 5, 2010, 3:48pm

No, you will require a special USB cable and in practice, getting USB
debugging to harder than the other two types, because you many only use port
0, which can be hard to find (and isn’t even necessarily available,
depending on the particular system).

I would strongly recommend that you go with 1394 debugging, if it is an
option, and you require an ACTUAL physical machine. If you can use a VM
(basically, if you’re debugging something that doesn’t use real hardware -
FS, FSF, et. c.) then I would strongly recommend that you got with VMWare
and VirtualKD.

The ‘NET’ option isn’t an option - it was apparently part of some experiment
that never saw the light of day.

Good luck,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Tuesday, October 05, 2010 3:24 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Debuggee not connected, bp not supported

Paul,

Thank you for your suggestion. I will read the tutorial.

" No IP, serial debug cable, 1394 or VM are your only options to debug."

The first thing I noticed in the debugging kernel tutorial you mentioned, is
that when it shows the kernel debugging dialog, it only has tabs for COM,
1394 and Local. While I have tabs for USB 2.0 and NET.

I think mm mentioned something about USB cables (that I have a lot of),
can’t they be used? Must they be “special” and in what way?

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

OSR_Community_User · October 5, 2010, 4:14pm

Hello mm,

Thank you. Yes, I was wondering about that USB debugging, it seems to be fussy about where the USB devices connect (and I need to wait for that new cable which apparently only PLX supplies).

As far as virtual machine option is concerned which would apply to my situation (I don’t directly speak to hardware), would VirtualBox be a good choice? I see it mentioned in the Virtual Kd doc.

mm1 · October 5, 2010, 4:17pm

I know of at least one person that has had success with that setup
(VirtualKD + VirtualBox), though as I recall it took a little doing. I know
of many (including myself) that have had no trouble getting the VirtualKD +
VMWare configuration working, but that being said, VMWare is obviously not
free.

Good luck,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Tuesday, October 05, 2010 4:12 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Debuggee not connected, bp not supported

Hello mm,

Thank you. Yes, I was wondering about that USB debugging, it seems to be
fussy about where the USB devices connect (and I need to wait for that new
cable which apparently only PLX supplies).

As far as virtual machine option is concerned which would apply to my
situation (I don’t directly speak to hardware), would VirtualBox be a good
choice? I see it mentioned in the Virtual Kd doc.

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer