Symbol file loading

Hi all,

I’m new in Windbg. I’ve setup and configured Windbg correctly, target and host machines in a kernel debug mode are connected and debugging started.
After connection between target and host, an error with the follow message was appear:
“ERROR: Symbol file could not be found. Default to export symbols for ntkrnlmp.exe”.
When I want to set a break point, a message box appears with this message:
“Symbol information for the current line could not be located in the currently loaded symbols.”
and break point could not set.

I’ve compiled device driver code with VC6 and the OS is Windows 2000.
How can I find or create the desired symbol files?

Thanks
Alireza

You mean you compiled it with vssbuild tool ? anyway you have to set the
path to the pdb file for your driver and OS files for proper debugging. read
the “kernel_debugging_tutorial.doc” available in the windbg folder to know
simple commands.
use “.symfix <symbol_storage_folder_path>” , this will set the url for
symbol server and download the OS symbols and use directly.
also use “.sympath+ <path_to_your_pdb>” to load the symbol file for your
driver.

rtshiva

On Sun, Sep 13, 2009 at 2:40 PM, wrote:

> Hi all,
>
> I’m new in Windbg. I’ve setup and configured Windbg correctly, target and
> host machines in a kernel debug mode are connected and debugging started.
> After connection between target and host, an error with the follow message
> was appear:
> “ERROR: Symbol file could not be found. Default to export symbols for
> ntkrnlmp.exe”.
> When I want to set a break point, a message box appears with this message:
> “Symbol information for the current line could not be located in the
> currently loaded symbols.”
> and break point could not set.
>
> I’ve compiled device driver code with VC6 and the OS is Windows 2000.
> How can I find or create the desired symbol files?
>
> Thanks
> Alireza
>
> —
> 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
></path_to_your_pdb></symbol_storage_folder_path>

Building directly in VC or VS is not supported. Iirc, the pdb symbol format changed after VC6 so if you are building with its compiler (vs using osr’s or hollistech’s batch script which let’s you build in the wdk but use the IDE to edit code) it might not work after you fix your sympath

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

-----Original Message-----
From: xxxxx@BasamadCo.com
Sent: Sunday, September 13, 2009 2:10 AM
To: Kernel Debugging Interest List
Subject: [windbg] Symbol file loading

Hi all,

I’m new in Windbg. I’ve setup and configured Windbg correctly, target and host machines in a kernel debug mode are connected and debugging started.
After connection between target and host, an error with the follow message was appear:
“ERROR: Symbol file could not be found. Default to export symbols for ntkrnlmp.exe”.
When I want to set a break point, a message box appears with this message:
“Symbol information for the current line could not be located in the currently loaded symbols.”
and break point could not set.

I’ve compiled device driver code with VC6 and the OS is Windows 2000.
How can I find or create the desired symbol files?

Thanks
Alireza


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

I do hope he reads Doron’s comment first. His primary problem is an invalid
build environment, which more than likely will solve the symbols problem.
Drivers should be built with the compiler in the DDK and now WDK and NOT the
compiler in VC++ or Visual Studio. Either use the build environments in the
WDK or download DDKBUILD from OsrOnline or Hollistech and build using the
proper environment. Using DDKBUILD you can keep things “legal” and still use
your editor du jour.

The personal opinion of

Gary G. Little

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of sivakumar
thulasimani
Sent: Sunday, September 13, 2009 4:38 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Symbol file loading

You mean you compiled it with vssbuild tool ? anyway you have to set the
path to the pdb file for your driver and OS files for proper debugging. read
the “kernel_debugging_tutorial.doc” available in the windbg folder to know
simple commands.

use “.symfix <symbol_storage_folder_path>” , this will set the url for
symbol server and download the OS symbols and use directly.

also use “.sympath+ <path_to_your_pdb>” to load the symbol file for your
driver.

rtshiva

On Sun, Sep 13, 2009 at 2:40 PM, wrote:

Hi all,

I’m new in Windbg. I’ve setup and configured Windbg correctly, target and
host machines in a kernel debug mode are connected and debugging started.
After connection between target and host, an error with the follow message
was appear:
“ERROR: Symbol file could not be found. Default to export symbols for
ntkrnlmp.exe”.
When I want to set a break point, a message box appears with this message:
“Symbol information for the current line could not be located in the
currently loaded symbols.”
and break point could not set.

I’ve compiled device driver code with VC6 and the OS is Windows 2000.
How can I find or create the desired symbol files?

Thanks
Alireza


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

Information from ESET Smart Security, version of virus signature
database 4422 (20090913)


The message was checked by ESET Smart Security.

http://www.eset.com</path_to_your_pdb></symbol_storage_folder_path>

>>Building directly in VC or VS is not supported. Iirc, the pdb symbol format changed after VC6 so if you >>are building with its compiler (vs using osr’s or hollistech’s batch script which let’s you build in the >>but use the IDE to edit code) it might not work after you fix your sympath

+1

You definitely should not be using VC to build any driver, no matter what the version. As a few people have pointed out, using Mark’s/OSR ddkbuild.bat is fine, because you’re not really using VC, just VS, but otherwise, this is a definite no-no.

That being said, have you set a symbol path at all. Something like:

!sym noisy
.sympath srv*c:\sym*http://msdl.microsoft.com/download/symbols
.reload -f -n
lml

Good luck,

mm