StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWinDbg Dr. Watson minidump - requires pdb/dll originally built for installed version?
primarykey
Id
134866
data
AcceptedAnswerId
134928
AnswerCount
5
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-09-25T17:57:18.927
FavoriteCount
4
LastActivityDate
2014-01-13T19:32:21.960
LastEditDate
2008-10-08T20:24:15.700
LastEditorUserId
21632
OwnerUserId
8123
ParentId
0
PostTypeId
1
Score
3
ViewCount
6901
LastEditorDisplayName
Adam Bellaire
text
Body
I have a mindmp file from a target's application crash. Is it possible for me to rebuild the dll/pdb files for a version of software and have windbg load symbols correctly? My problem is that our pdb files are only kept for major releases (unfortunately). This is a daily build, which I can rebuild myself, but I'm getting tripped up on errors. With !sym noisy on: "image header does not match memory image header." <pre><code>DBGENG: C:\...\XXX.dll image header does not match memory image header. DBGENG: XXX.dll - Partial symbol image load missing image info DBGHELP: Module is not fully loaded into memory. DBGHELP: Searching for symbols using debugger-provided data. DBGHELP: C:\...\XXX.pdb - mismatched pdb </code></pre> Note I've build the pdb with the dll, they are from the same RELEASE directory (should I be building debug?) Theses are release builds (as release builds are installed on the target and crashing) should I be somehow using the debug build dlls to get more symbol information?
Tags
<windows><debugging><dll><windbg><dr.watson>
Title
WinDbg Dr. Watson minidump - requires pdb/dll originally built for installed version?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAdam Bellaire
UserOwnerUserId
1. USDoug T.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
3. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.