Re: can't see source code in WinDbg

[Andre Vachon [MS]]

use the "ln" command to get the source information about a symbol.

ln <address | symbol>

will tell you the symbol as well as source information for it.
If you see no source line, it means the source information is not available
in the PDB.
If the source information is there, make sure the path does point to the
source, or reset the root of the path using the .srcpath command in the
debugger.

-Andre
--
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2004 Microsoft Corporation. All rights
reserved.

"Li" <anon...@discussions.microsoft.com> wrote in message
news:73671E0C-78DF-48E7...@microsoft.com...
> Hi, all. I am trying to debug my mouse driver, but I can't see my source
code in C, only assemly. The output from WinDbg is as following. It seems to
me the connection ans symbols are OK. Anyone knows what's the problem?
There is an message under the command window saying "Debugee not
connected". It confused me since the message in the command window says
"connection established".
>
> This question may sounds silly, but I just couldn't find any definite
answer in the WinDbg help. Do I have to load the driver I'm debugging on the
target machine before I start debugging? I tried both ways and I can't see
my source code with or without loading my driver.
>
> Thanks in advance for your help.
>
> Li
> ---------------------
> Opened \\.\Com1
> Waiting to reconnect...
> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
> Kernel Debugger connection established.
> Symbol search path is:
srv*DownStreamStore*http://msdl.microsoft.com/download/symbols;C:\myMouseDri
ver\objchk\i386\moufiltr.pdb
> Executable search path is: C:\myMouseDriver\objchk\i386\moufiltr.sys
> Windows XP Kernel Version 2600 UP Free x86 compatible
> Built by: 2600.xpclient.010817-1148
> Kernel base = 0x804d0000 PsLoadedModuleList = 0x80545b28
> System Uptime: not available
> Symbol search path is:
SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols;c:\winddk\260
0\src\input\moufiltr\objchk\i386
>

[Andre Vachon [MS]]

In the example below it looks like you may be setting a breakpoint on
DriverEntry after it's been executed.
You need to set the breakpoint before the module is loaded. The best way to
do that is to breakin early and do

bu moufiltr!DriverEntry
g

-Andre

"Li" <anon...@discussions.microsoft.com> wrote in message

news:B92AF44E-514C-4788...@microsoft.com...
> Thanks for your advice. I tried "ln" command and I can see the source code
info. But my source window won't show during the dubugging. When I mannually
open my source file, I can see the breakpoints I set with "bp" are
highlighted in red. But when I tried to step through my source code, nothing
happened. No blue bar moving anywhere. And the breakpoint doesn't look like
being hit. The windbg output is followed. Do you know what I might be doing
wrong? Why does the warning say the files are not accessible while I can use
"ln" command to see my source code? How do I make them accessible?
>
> ------
> WARNING: C:\myMouseDriver\objchk\i386\moufiltr.sys is not accessible
> Symbol search path is:
SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols;;C:\myMouseDr
iver\objchk\i386\moufiltr.pdb
> WARNING: Path element is empty
> WARNING: C:\myMouseDriver\objchk\i386\moufiltr.pdb is not accessible
> WARNING: Path element is empty
> WARNING: C:\myMouseDriver\objchk\i386\moufiltr.pdb is not accessible
> Break instruction exception - code 80000003 (first chance)
>
****************************************************************************
***
> *
*
> * You are seeing this message because you pressed either
*
> * CTRL+C (if you run kd.exe) or,
*
> * CTRL+BREAK (if you run WinDBG),
*
> * on your debugger machine's keyboard.
*
> *
*
> * THIS IS NOT A BUG OR A SYSTEM CRASH
*
> *
*
> * If you did not intend to break into the debugger, press the "g" key,
then *
> * press the "Enter" key now. This message might immediately reappear. If
it *
> * does, press "g" and "Enter" again.
*
> *
*
>
****************************************************************************
***
> nt!RtlpBreakWithStatusInstruction:
> 8050d064 cc int 3
> kd> ln moufiltr!DriverEntry
> c:\mymousedriver\moufiltr.c(45)
> (fe32b300) moufiltr!DriverEntry | (fe32b388)
moufiltr!_IMPORT_DESCRIPTOR_ntoskrnl
> Exact matches:
> moufiltr!DriverEntry (_DRIVER_OBJECT*, _UNICODE_STRING*)
> kd> bp moufiltr!DriverEntry
> kd> g
>
> ----- Andre Vachon [MS] wrote: -----