Beginners help with WinDbg

[Aaron]

I'm trying to debug a sample Bulk USB Device driver. I have hardware I need,
attached to my pc. I created a new workspace in WinDbg, setup the symbol file
path, the image file path and source file path. The symbols seem to load
correctly. When I go to teh WinDbg command window and do an lml I see my .sys
file name and next to it I see "(private pdb symbols)" along with the correct
directory. However, when I open up a source file and click on the breakpoint
button (the hand) nothing happens.
When I click the run button I get the message "No runnable debuggees error
in 'g'"
It seems as though I can't attach my source code to my pdb or sys files. Can
anyone help me?

[Ivan Brugiolo [MSFT]]

Since this is really basic, try to break on module load
kd> sxe ld <mudulename>
Then, on module-load event, try to set your breakpoints.
The first breakpoint that will hit is <modulename>!DriverEntry.

Then depending on the style of your driver, you might have the AddDevice
routine, or any of the Dispatch Routine that you have registered.

Sometimes improperly written driver are unloaded immediately after
DriverEntry is called, so, set a breakpoint in the Unload routine as well.

--

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Aaron" <Aa...@discussions.microsoft.com> wrote in message
news:375187F5-840B-4DB7...@microsoft.com...

[Kalle Olavi Niemitalo]

Aaron <Aa...@discussions.microsoft.com> writes:

> When I click the run button I get the message "No runnable debuggees error
> in 'g'"

Are you debugging the kernel on the local computer? For proper
kernel debugging with breakpoints, you need two computers
(but perhaps they can be virtual).