Comments on: Crash Dump Analysis Patterns (Part 153) https://www.dumpanalysis.org/blog/index.php/2011/10/21/crash-dump-analysis-patterns-part-153/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Wed, 06 May 2026 15:03:58 +0000 http://wordpress.org/?v=2.3.3 By: Dmitry Vostokov https://www.dumpanalysis.org/blog/index.php/2011/10/21/crash-dump-analysis-patterns-part-153/#comment-359535 Dmitry Vostokov Mon, 24 Oct 2011 21:37:35 +0000 https://www.dumpanalysis.org/blog/index.php/2011/10/21/crash-dump-analysis-patterns-part-153/#comment-359535 I copy the whole folder just in case if there are any extra dependencies I copy the whole folder just in case if there are any extra dependencies

]]> By: Marc Sherman https://www.dumpanalysis.org/blog/index.php/2011/10/21/crash-dump-analysis-patterns-part-153/#comment-359399 Marc Sherman Mon, 24 Oct 2011 17:27:18 +0000 https://www.dumpanalysis.org/blog/index.php/2011/10/21/crash-dump-analysis-patterns-part-153/#comment-359399 Yes, managed debugging requires that the analysis machine use the same bitness and framework as the dump machine. When you say you "copy" the framework, what exactly do you copy? A subset of the binaries or all of them? thanks Yes, managed debugging requires that the analysis machine use the same bitness and framework as the dump machine. When you say you “copy” the framework, what exactly do you copy? A subset of the binaries or all of them?

thanks

]]> By: Dmitry Vostokov https://www.dumpanalysis.org/blog/index.php/2011/10/21/crash-dump-analysis-patterns-part-153/#comment-359369 Dmitry Vostokov Mon, 24 Oct 2011 16:21:30 +0000 https://www.dumpanalysis.org/blog/index.php/2011/10/21/crash-dump-analysis-patterns-part-153/#comment-359369 The dump came from another machine where mscorwks and sos were the same version of course. On the analysis machine we have a different version of framework installed with a different sos. So we have a discrepancy between the version of the mscorwks in the dump and sos on the analysis machine. So we copy the correct version of the framework from the machine the dump came from. Please check this pattern: http://www.dumpanalysis.org/blog/index.php/2011/06/01/crash-dump-analysis-patterns-part-136/ The dump came from another machine where mscorwks and sos were the same version of course. On the analysis machine we have a different version of framework installed with a different sos. So we have a discrepancy between the version of the mscorwks in the dump and sos on the analysis machine. So we copy the correct version of the framework from the machine the dump came from. Please check this pattern:
http://www.dumpanalysis.org/blog/index.php/2011/06/01/crash-dump-analysis-patterns-part-136/

]]> By: Marc Sherman https://www.dumpanalysis.org/blog/index.php/2011/10/21/crash-dump-analysis-patterns-part-153/#comment-359292 Marc Sherman Mon, 24 Oct 2011 14:05:22 +0000 https://www.dumpanalysis.org/blog/index.php/2011/10/21/crash-dump-analysis-patterns-part-153/#comment-359292 I thought the version of sos.dll that lives in the same folder as mscorwks.dll is always the correct one. It looks like, from your folder path names, that mscorwks.dll was updated but sos.dll was not. If so, how did you get the correct version of sos.dll? thanks I thought the version of sos.dll that lives in the same folder as mscorwks.dll is always the correct one. It looks like, from your folder path names, that mscorwks.dll was updated but sos.dll was not. If so, how did you get the correct version of sos.dll?

thanks

]]>