Windbg - symbols mismatched - help (is it a build issue)

WINDBG
1

Hi guys,

I have build the Vista driver with “Windows Vista x86 Checked Build Environment” which I expected would be good enough to debug the driver with Windbg.

I loaded my driver on Target Machine, started a debug session on a serial port connected system.
CTRL+Break it.

kd > .reload /f waclient.sys
kd > lm sm wa*
906c4000 906d0000 waclient (no symbols)

kd > !sym noisy
kd > .reload /f /i waclient.sys
…
DBGHELP: Loaded mismatched pdb for waclient.sys
DBGENG: waclient.sys has mismatched symbols - type “.hh dbgerr003” for details
DBGHELP: waclient - private symbols & lines
C:\Windows_driver_devel\objchk_wlh_x86\i386\waclient.pdb - unmatched
kd > lm sm wa*
906c4000 906d0000 waclient (no symbols)

Still no symbols.
Why are the symbols getting mismatched?
Am I missing some flags at the compile/link stage?

  • Mukund Jampala
2

What’s the output from “!chksym waclient C:\Windows_driver_devel\objchk_wlh_x86\i386\waclient.pdb”?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Thursday, October 08, 2009 06:12 PM
To: Kernel Debugging Interest List
Subject: [windbg] Windbg - symbols mismatched - help (is it a build issue)

Hi guys,

I have build the Vista driver with “Windows Vista x86 Checked Build Environment” which I expected would be good enough to debug the driver with Windbg.

I loaded my driver on Target Machine, started a debug session on a serial port connected system.
CTRL+Break it.

kd > .reload /f waclient.sys
kd > lm sm wa*
906c4000 906d0000 waclient (no symbols)

kd > !sym noisy
kd > .reload /f /i waclient.sys
…
DBGHELP: Loaded mismatched pdb for waclient.sys
DBGENG: waclient.sys has mismatched symbols - type “.hh dbgerr003” for details
DBGHELP: waclient - private symbols & lines
C:\Windows_driver_devel\objchk_wlh_x86\i386\waclient.pdb - unmatched
kd > lm sm wa*
906c4000 906d0000 waclient (no symbols)

Still no symbols.
Why are the symbols getting mismatched?
Am I missing some flags at the compile/link stage?

  • Mukund Jampala

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

3

Thanks Jen-Lung,

That helped. Got the problem.

Here is what u asked.
kd> !chksym waclient

waclient.sys
Timestamp: 4ABA09D9
SizeOfImage: C000
pdb: d:\builds\src\drv_vi~1\objfre_wlh_x86\i386\waclient.pdb
pdb sig: 07344B0D-277E-4FB5-A467-3E5DC110C309
age: 1
kd> !lmi waclient
Time Stamp: 4aba09d9 Wed Sep 23 04:43:21 2009 // which is way old.

I don’t have a “D:” at all. So, it was one of my old builds in a different Machine.

Issue was:
When ever I build the driver, it gets copied to a different location.
I load the driver from that location. For some reason, the existing driver file was NOT being over-written.

I guess it should be ok now. right now i am rebuilding my app/driver.

Is there a utility to look into the PDB files.
At times when symbols do not match, is there a work around to look into the PDB file and match it with results of !Analyze -v.
What I all want is who it it and where is it?

  • Mukund Jampala
4

Hi Jen-Lung,

I have the symbols loading properly.
I noticed that in the ‘!lmi waclient’ it shows as follows:

Load Report: private symbols & lines, not source indexed
What build options do I have to use so that debuffer has source indexing info too.
What should I put the sources file.

kd> !lmi waclient
Loaded Module Info: [waclient]
Module: waclient
Base Address: 8bdda000
Image Name: waclient.sys
Machine Type: 332 (I386)
Time Stamp: 4acf6b66 Fri Oct 09 09:57:10 2009
Size: 14000
CheckSum: 1d20b
Characteristics: 102
Debug Data Dirs: Type Size VA Pointer
CODEVIEW 9d, d4f8, c0f8 RSDS - GUID: {B611B4E5-AF12-449F-9C53-D428D22C89B8}
Age: 1, Pdb: C:\Windows_driver_devel\objchk_wlh_x86\i386\waclient.pdb
Image Type: MEMORY - Image read successfully from loaded memory.
Symbol Type: PDB - Symbols loaded successfully from symbol search path.
C:\Windows_driver_devel\objchk_wlh_x86\i386\waclient.pdb
Compiler: Resource - front end [0.0 bld 0] - back end [8.0 bld 50727]
Load Report: private symbols & lines, not source indexed
C:\Windows_driver_devel\objchk_wlh_x86\i386\waclient.pdb

Thanks,
Mukund Jampala

5

Check srcsrv.doc in “\srcsrv”. Thanks,

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Friday, October 09, 2009 04:17 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Windbg - symbols mismatched - help (is it a build issue)

Hi Jen-Lung,

I have the symbols loading properly.
I noticed that in the ‘!lmi waclient’ it shows as follows:

Load Report: private symbols & lines, not source indexed
What build options do I have to use so that debuffer has source indexing info too.
What should I put the sources file.

kd> !lmi waclient
Loaded Module Info: [waclient]
Module: waclient
Base Address: 8bdda000
Image Name: waclient.sys
Machine Type: 332 (I386)
Time Stamp: 4acf6b66 Fri Oct 09 09:57:10 2009
Size: 14000
CheckSum: 1d20b
Characteristics: 102
Debug Data Dirs: Type Size VA Pointer
CODEVIEW 9d, d4f8, c0f8 RSDS - GUID: {B611B4E5-AF12-449F-9C53-D428D22C89B8}
Age: 1, Pdb: C:\Windows_driver_devel\objchk_wlh_x86\i386\waclient.pdb
Image Type: MEMORY - Image read successfully from loaded memory.
Symbol Type: PDB - Symbols loaded successfully from symbol search path.
C:\Windows_driver_devel\objchk_wlh_x86\i386\waclient.pdb
Compiler: Resource - front end [0.0 bld 0] - back end [8.0 bld 50727]
Load Report: private symbols & lines, not source indexed
C:\Windows_driver_devel\objchk_wlh_x86\i386\waclient.pdb

Thanks,
Mukund Jampala

—
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