Mismatched pdb problem

I’m trying to analyze crashdump using WinDbg 6.2.0013.0. Crash was caused by
old version of my driver which I don’t have but can rebuild the exact binary
from VCS archives. Binary was built, the same size and contents and
different timestamps. WinDbg refuses to load symbols for this driver:

kd> .reload /f /v tcusb.sys
AddImage: \SystemRoot\System32\Drivers\tcusb.sys
DllBase = f9d83000
Size = 00004200
Checksum = 0000c380
TimeDateStamp = 3f960033
SYMSRV:
http://msdl.microsoft.com/download/symbols/tcusb.pdb/072A391CEAE04B629063529
DE62C682C1/tcusb.pd_ not found
DBGHELP: d:\usb\bsod\jim\tcusb.pdb - mismatched pdb
DBGHELP: d:\usb\bsod\jim\symbols\sys\tcusb.pdb - file not found
DBGHELP: d:\usb\bsod\jim\sys\tcusb.pdb - file not found
DBGHELP: D:\usb\stusb\objfre_wxp_x86\i386\tcusb.pdb - mismatched pdb
DBGHELP: Couldn’t load mismatched pdb for tcusb.sys
*** ERROR: Module load completed but symbols could not be loaded for
tcusb.sys
DBGHELP: tcusb - no symbols loaded

Both mentioned PDBs are correct (the same) from driver rebuild. I’m quite
sure they could be used with no problem but don’t know how to persuade
WinDbg to use it. Visual SoftICE claims the problem is caused by mismatched
GUIDs so I guess they are used for identification of the same build. Well,
it makes sense but what to do in my situation? Any idea?

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

Never mind. I just found /i switch for .reload command and PDB is finally
loaded. Don’t know how could miss it before…

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]


From: Michal Vodicka
Sent: Tuesday, October 28, 2003 10:19 PM
To: ‘xxxxx@lists.osr.com’
Subject: Mismatched pdb problem

I’m trying to analyze crashdump using WinDbg 6.2.0013.0. Crash was caused
by old version of my driver which I don’t have but can rebuild the exact
binary from VCS archives. Binary was built, the same size and contents and
different timestamps. WinDbg refuses to load symbols for this driver:

kd> .reload /f /v tcusb.sys
AddImage: \SystemRoot\System32\Drivers\tcusb.sys
DllBase = f9d83000
Size = 00004200
Checksum = 0000c380
TimeDateStamp = 3f960033
SYMSRV:
http://msdl.microsoft.com/download/symbols/tcusb.pdb/072A391CEAE04B6290635
29DE62C682C1/tcusb.pd_ not found
DBGHELP: d:\usb\bsod\jim\tcusb.pdb - mismatched pdb
DBGHELP: d:\usb\bsod\jim\symbols\sys\tcusb.pdb - file not found
DBGHELP: d:\usb\bsod\jim\sys\tcusb.pdb - file not found
DBGHELP: D:\usb\stusb\objfre_wxp_x86\i386\tcusb.pdb - mismatched pdb
DBGHELP: Couldn’t load mismatched pdb for tcusb.sys
*** ERROR: Module load completed but symbols could not be loaded for
tcusb.sys
DBGHELP: tcusb - no symbols loaded

Both mentioned PDBs are correct (the same) from driver rebuild. I’m quite
sure they could be used with no problem but don’t know how to persuade
WinDbg to use it. Visual SoftICE claims the problem is caused by
mismatched GUIDs so I guess they are used for identification of the same
build. Well, it makes sense but what to do in my situation? Any idea?

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

It crappens.

=====================
Mark Roddy

-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Tuesday, October 28, 2003 4:27 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] RE: Mismatched pdb problem

Never mind. I just found /i switch for .reload command and
PDB is finally loaded. Don’t know how could miss it before…

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

> ----------
> From: Michal Vodicka
> Sent: Tuesday, October 28, 2003 10:19 PM
> To: ‘xxxxx@lists.osr.com’
> Subject: Mismatched pdb problem
>
> I’m trying to analyze crashdump using WinDbg 6.2.0013.0. Crash was
> caused by old version of my driver which I don’t have but
can rebuild
> the exact binary from VCS archives. Binary was built, the same size
> and contents and different timestamps. WinDbg refuses to
load symbols
> for this driver:
>
> kd> .reload /f /v tcusb.sys
> AddImage: \SystemRoot\System32\Drivers\tcusb.sys
> DllBase = f9d83000
> Size = 00004200
> Checksum = 0000c380
> TimeDateStamp = 3f960033
> SYMSRV:
>
http://msdl.microsoft.com/download/symbols/tcu\> sb.pdb/072A391CEAE04B629
> 0635
> 29DE62C682C1/tcusb.pd_ not found
> DBGHELP: d:\usb\bsod\jim\tcusb.pdb - mismatched pdb
> DBGHELP: d:\usb\bsod\jim\symbols\sys\tcusb.pdb - file not found
> DBGHELP: d:\usb\bsod\jim\sys\tcusb.pdb - file not found
> DBGHELP: D:\usb\stusb\objfre_wxp_x86\i386\tcusb.pdb - mismatched pdb
> DBGHELP: Couldn’t load mismatched pdb for tcusb.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> tcusb.sys
> DBGHELP: tcusb - no symbols loaded
>
> Both mentioned PDBs are correct (the same) from driver rebuild. I’m
> quite sure they could be used with no problem but don’t know how to
> persuade WinDbg to use it. Visual SoftICE claims the
problem is caused
> by mismatched GUIDs so I guess they are used for
identification of the
> same build. Well, it makes sense but what to do in my
situation? Any
> idea?
>
> Best regards,
>
> Michal Vodicka
> STMicroelectronics Design and Application s.r.o.
> [michal.vodicka@st.com, http:://www.st.com]
>
>


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

Huh? Sorry, I don’t understand. Now it works with no problem.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]


From: xxxxx@stratus.com[SMTP:xxxxx@stratus.com]
Reply To: xxxxx@lists.osr.com
Sent: Tuesday, October 28, 2003 10:43 PM
To: xxxxx@lists.osr.com
Subject: [ntdev] RE: Mismatched pdb problem

It crappens.

=====================
Mark Roddy

> -----Original Message-----
> From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
> Sent: Tuesday, October 28, 2003 4:27 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] RE: Mismatched pdb problem
>
>
> Never mind. I just found /i switch for .reload command and
> PDB is finally loaded. Don’t know how could miss it before…
>
> Best regards,
>
> Michal Vodicka
> STMicroelectronics Design and Application s.r.o.
> [michal.vodicka@st.com, http:://www.st.com]
>
> > ----------
> > From: Michal Vodicka
> > Sent: Tuesday, October 28, 2003 10:19 PM
> > To: ‘xxxxx@lists.osr.com’
> > Subject: Mismatched pdb problem
> >
> > I’m trying to analyze crashdump using WinDbg 6.2.0013.0. Crash was
> > caused by old version of my driver which I don’t have but
> can rebuild
> > the exact binary from VCS archives. Binary was built, the same size
> > and contents and different timestamps. WinDbg refuses to
> load symbols
> > for this driver:
> >
> > kd> .reload /f /v tcusb.sys
> > AddImage: \SystemRoot\System32\Drivers\tcusb.sys
> > DllBase = f9d83000
> > Size = 00004200
> > Checksum = 0000c380
> > TimeDateStamp = 3f960033
> > SYMSRV:
> >
> http://msdl.microsoft.com/download/symbols/tcu\> sb.pdb/072A391CEAE04B629
> > 0635
> > 29DE62C682C1/tcusb.pd_ not found
> > DBGHELP: d:\usb\bsod\jim\tcusb.pdb - mismatched pdb
> > DBGHELP: d:\usb\bsod\jim\symbols\sys\tcusb.pdb - file not found
> > DBGHELP: d:\usb\bsod\jim\sys\tcusb.pdb - file not found
> > DBGHELP: D:\usb\stusb\objfre_wxp_x86\i386\tcusb.pdb - mismatched pdb
> > DBGHELP: Couldn’t load mismatched pdb for tcusb.sys
> > *** ERROR: Module load completed but symbols could not be loaded for
> > tcusb.sys
> > DBGHELP: tcusb - no symbols loaded
> >
> > Both mentioned PDBs are correct (the same) from driver rebuild. I’m
> > quite sure they could be used with no problem but don’t know how to
> > persuade WinDbg to use it. Visual SoftICE claims the
> problem is caused
> > by mismatched GUIDs so I guess they are used for
> identification of the
> > same build. Well, it makes sense but what to do in my
> situation? Any
> > idea?
> >
> > Best regards,
> >
> > Michal Vodicka
> > STMicroelectronics Design and Application s.r.o.
> > [michal.vodicka@st.com, http:://www.st.com]
> >
> >
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: michal.vodicka@st.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Not rtfm’ing happens. Sorry for the ambiguity. Lame humor. Nevermind.

=====================
Mark Roddy

-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Tuesday, October 28, 2003 5:53 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] RE: Mismatched pdb problem

Huh? Sorry, I don’t understand. Now it works with no problem.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

> ----------
> From: xxxxx@stratus.com[SMTP:xxxxx@stratus.com]
> Reply To: xxxxx@lists.osr.com
> Sent: Tuesday, October 28, 2003 10:43 PM
> To: xxxxx@lists.osr.com
> Subject: [ntdev] RE: Mismatched pdb problem
>
> It crappens.
>
> =====================
> Mark Roddy
>
>
> > -----Original Message-----
> > From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
> > Sent: Tuesday, October 28, 2003 4:27 PM
> > To: Windows System Software Devs Interest List
> > Subject: [ntdev] RE: Mismatched pdb problem
> >
> >
> > Never mind. I just found /i switch for .reload command and
> > PDB is finally loaded. Don’t know how could miss it before…
> >
> > Best regards,
> >
> > Michal Vodicka
> > STMicroelectronics Design and Application s.r.o.
> > [michal.vodicka@st.com, http:://www.st.com]
> >
> > > ----------
> > > From: Michal Vodicka
> > > Sent: Tuesday, October 28, 2003 10:19 PM
> > > To: ‘xxxxx@lists.osr.com’
> > > Subject: Mismatched pdb problem
> > >
> > > I’m trying to analyze crashdump using WinDbg
6.2.0013.0. Crash was
> > > caused by old version of my driver which I don’t have but
> > can rebuild
> > > the exact binary from VCS archives. Binary was built, the same
> > > size
> > > and contents and different timestamps. WinDbg refuses to
> > load symbols
> > > for this driver:
> > >
> > > kd> .reload /f /v tcusb.sys
> > > AddImage: \SystemRoot\System32\Drivers\tcusb.sys
> > > DllBase = f9d83000
> > > Size = 00004200
> > > Checksum = 0000c380
> > > TimeDateStamp = 3f960033
> > > SYMSRV:
> > >
> > http://msdl.microsoft.com/download/symbols/tcu\>
> > sb.pdb/072A391CEAE04B629
> > > 0635
> > > 29DE62C682C1/tcusb.pd_ not found
> > > DBGHELP: d:\usb\bsod\jim\tcusb.pdb - mismatched pdb
> > > DBGHELP: d:\usb\bsod\jim\symbols\sys\tcusb.pdb - file not found
> > > DBGHELP: d:\usb\bsod\jim\sys\tcusb.pdb - file not found
> > > DBGHELP: D:\usb\stusb\objfre_wxp_x86\i386\tcusb.pdb -
mismatched
> > > pdb
> > > DBGHELP: Couldn’t load mismatched pdb for tcusb.sys
> > > *** ERROR: Module load completed but symbols could not
be loaded for
> > > tcusb.sys
> > > DBGHELP: tcusb - no symbols loaded
> > >
> > > Both mentioned PDBs are correct (the same) from driver rebuild.
> > > I’m
> > > quite sure they could be used with no problem but don’t
know how to
> > > persuade WinDbg to use it. Visual SoftICE claims the
> > problem is caused
> > > by mismatched GUIDs so I guess they are used for
> > identification of the
> > > same build. Well, it makes sense but what to do in my
> > situation? Any
> > > idea?
> > >
> > > Best regards,
> > >
> > > Michal Vodicka
> > > STMicroelectronics Design and Application s.r.o.
> > > [michal.vodicka@st.com, http:://www.st.com]
> > >
> > >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@stratus.com To
> unsubscribe send a blank email to xxxxx@lists.osr.com
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: michal.vodicka@st.com To
> unsubscribe send a blank email to xxxxx@lists.osr.com
>


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to xxxxx@lists.osr.com