https://www.dumpanalysis.org/blog/index.php/2008/05/27/10-common-mistakes-in-memory-analysis-part-1/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Wed, 06 May 2026 12:50:26 +0000 http://wordpress.org/?v=2.3.3 https://www.dumpanalysis.org/blog/index.php/2008/05/27/10-common-mistakes-in-memory-analysis-part-1/#comment-119993 Crash Dump Analysis » Blog Archive » Mode-independent WinDbg scripts Fri, 29 Jan 2010 00:13:37 +0000 https://www.dumpanalysis.org/blog/index.php/2008/05/27/10-common-mistakes-in-memory-analysis-part-1/#comment-119993 [...] first command eliminates the common mistake of truncated traces. The second commands fails for process user memory dumps but shows full 3-parameter stack [...] […] first command eliminates the common mistake of truncated traces. The second commands fails for process user memory dumps but shows full 3-parameter stack […]

]]> https://www.dumpanalysis.org/blog/index.php/2008/05/27/10-common-mistakes-in-memory-analysis-part-1/#comment-108498 Crash Dump Analysis » Blog Archive » 10 Common Mistakes in Memory Analysis (Part 6) Tue, 08 Dec 2009 11:14:47 +0000 https://www.dumpanalysis.org/blog/index.php/2008/05/27/10-common-mistakes-in-memory-analysis-part-1/#comment-108498 [...] stack trace is empty here but look at all threads (we list full traces in order not to miss any module) we find one that shows a dialog box reporting a [...] […] stack trace is empty here but look at all threads (we list full traces in order not to miss any module) we find one that shows a dialog box reporting a […]

]]> https://www.dumpanalysis.org/blog/index.php/2008/05/27/10-common-mistakes-in-memory-analysis-part-1/#comment-48947 Crash Dump Analysis » Blog Archive » 10 Common Mistakes in Memory Analysis (Part 3) Wed, 29 Oct 2008 19:02:19 +0000 https://www.dumpanalysis.org/blog/index.php/2008/05/27/10-common-mistakes-in-memory-analysis-part-1/#comment-48947 [...] In part 1 we discussed the common mistake of not looking at full stack traces. In this part we discuss the mistake of not looking at all stack traces. This important when the dump is partially truncated or inconsistent. For example, in one complete memory dump from one hang system WinDbg !locks command is not able to traverse them at all due to truncated dump: [...] […] In part 1 we discussed the common mistake of not looking at full stack traces. In this part we discuss the mistake of not looking at all stack traces. This important when the dump is partially truncated or inconsistent. For example, in one complete memory dump from one hang system WinDbg !locks command is not able to traverse them at all due to truncated dump: […]

]]> https://www.dumpanalysis.org/blog/index.php/2008/05/27/10-common-mistakes-in-memory-analysis-part-1/#comment-38102 Crash Dump Analysis » Blog Archive » All at once: postmortem logs and dump files Fri, 15 Aug 2008 00:02:10 +0000 https://www.dumpanalysis.org/blog/index.php/2008/05/27/10-common-mistakes-in-memory-analysis-part-1/#comment-38102 [...] meta-command is necessary to avoid the common pitfall of looking at cut off stack traces (see Mistake #1). In addition to logging the output of any command we want, the script writes 4 memory dumps of [...] […] meta-command is necessary to avoid the common pitfall of looking at cut off stack traces (see Mistake #1). In addition to logging the output of any command we want, the script writes 4 memory dumps of […]

]]>