c# - How to read a crash dump file (I have source code and .pdb files) -
i have read questions on stackoverflow, still can't create work.
i have
a mini dump file customer the exact same version of our code client has got in debug directory, .pdb files code.i tried putting mini dump file in debug directory, opening in visual studio 2010. don't know if right thing do, or next.
"start debugging" greyed out in normal debug menu.
there box "actions" in top right hand corner of minidump file summary tab. clicked on "debug native only" "there no source code available current location."
i must missing simple - please can give me hint?
just pull various bits of info answer:
do have .pdb files created when programme built? rebuilding same source doesn't work, you need maintain .pdb files every build. – alex farber feb 20 '13 @ 11:05
"the debugger matches info filename, timestamp , checksum when matching pdb binary (dll or exe)." (saikat sen, codeproject article)
following alexfarber's hint, copied source code , release folder customer's build onto computer (the whole build had been saved, including .pdb , .exe files in release folder).
then copied dump file release folder, , loaded microsoft symbols same folder.
then opened dump file 1 time again visual studio 2010.
i didn't see more helpful before, assume due - see accepted reply on question. using c# , .net 2.0 assembly, , seems can view source code .net 4.0 assembly.
i seek windbg add-in called sos.dll recommended hans passant on same question next.
how round need utilize pdb files same build:
i think can round requirement same .pdb files if utilize windbg. virtualdub "if debugger stubborn , doesn't want load symbols because thinks don't match, can utilize .symopt+ 0x40 set "load anything" flag."
also, if understand correctly, can utilize chkmatch tool referred sergmat above, match .exe , .pdb files.
c# windows visual-studio-2010 crash minidump
No comments:
Post a Comment