https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Mon, 18 May 2026 00:43:47 +0000 http://wordpress.org/?v=2.3.3 https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-201561 Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 114) Tue, 09 Nov 2010 11:51:58 +0000 https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-201561 [...] Stack trace may or may not be included here and it might be incorrect, heuristic and not fully discernible automatically(requires raw stack semantic analysis) like in the example above. [...] […] Stack trace may or may not be included here and it might be incorrect, heuristic and not fully discernible automatically(requires raw stack semantic analysis) like in the example above. […]

]]> https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-154357 Crash Dump Analysis » Blog Archive » Icons for Memory Dump Analysis Patterns (Part 44) Fri, 28 May 2010 22:28:15 +0000 https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-154357 [...] Today we introduce an icon for Stack Trace pattern: [...] […] Today we introduce an icon for Stack Trace pattern: […]

]]> https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-86246 Crash Dump Analysis » Blog Archive » NULL data pointer, stack trace, inline function optimization and platformorphic fault: pattern cooperation Mon, 27 Jul 2009 20:04:53 +0000 https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-86246 [...] clearly have an instance of a NULL pointer data access. If we try to match this stack trace to known faults in database we would probably find many entries because memcpy is a generic [...] […] clearly have an instance of a NULL pointer data access. If we try to match this stack trace to known faults in database we would probably find many entries because memcpy is a generic […]

]]> https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-74273 Crash Dump Analysis » Blog Archive » Stack trace, invalid code pointer and hooked functions: pattern cooperation Wed, 13 May 2009 13:50:51 +0000 https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-74273 [...] crashed process we noticed an invalid code pointer. It is not a NULL code pointer but has the same stack trace [...] […] crashed process we noticed an invalid code pointer. It is not a NULL code pointer but has the same stack trace […]

]]> https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-72533 Crash Dump Analysis » Blog Archive » Trace Analysis Patterns (Part 1) Tue, 28 Apr 2009 09:23:23 +0000 https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-72533 [...] fact, stack traces and their collections are specializations of the more general traces. Another example [...] […] fact, stack traces and their collections are specializations of the more general traces. Another example […]

]]> https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-51733 Crash Dump Analysis » Blog Archive » Truncated dump, spiking thread, not my version and hooked functions: pattern cooperation Fri, 14 Nov 2008 19:54:18 +0000 https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-51733 [...] from Google search we can find that there is newer version available (variant of Not My Version pattern) and even [...] […] from Google search we can find that there is newer version available (variant of Not My Version pattern) and even […]

]]> https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-33782 Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 70) Thu, 10 Jul 2008 21:03:24 +0000 https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-33782 [...] instruction. Fortunately the rest of stack trace should be the same. Therefore when comparing Stack Traces we shouldn’t pay attention only to the top function call. This pattern is called Inline [...] […] instruction. Fortunately the rest of stack trace should be the same. Therefore when comparing Stack Traces we shouldn’t pay attention only to the top function call. This pattern is called Inline […]

]]> https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-33674 Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 69) Wed, 09 Jul 2008 17:49:54 +0000 https://www.dumpanalysis.org/blog/index.php/2007/09/10/crash-dump-analysis-patterns-part-25/#comment-33674 [...] patterns like Message Box and / or Stack Trace semantics reveal another pattern that I call Self-Diagnosis which may or may not result in [...] […] patterns like Message Box and / or Stack Trace semantics reveal another pattern that I call Self-Diagnosis which may or may not result in […]

]]>