https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Wed, 06 May 2026 21:35:56 +0000 http://wordpress.org/?v=2.3.3 https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-764001 Dmitry Vostokov Fri, 22 Jan 2021 22:35:37 +0000 https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-764001 We make this pattern name more specific by specifying its variant: Optimized Code (function parameter reuse). As a side note, this reuse mechanism is also used in tail recursion. We make this pattern name more specific by specifying its variant: Optimized Code (function parameter reuse). As a side note, this reuse mechanism is also used in tail recursion.

]]> https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-293345 Dmitry Vostokov Wed, 08 Jun 2011 20:55:50 +0000 https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-293345 Another example of parameter reuse: http://www.codemachine.com/article_paramreuse.html Another example of parameter reuse:
http://www.codemachine.com/article_paramreuse.html

]]> https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-135445 Crash Dump Analysis » Blog Archive » Icons for Memory Dump Analysis Patterns (Part 7) Thu, 18 Mar 2010 15:12:51 +0000 https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-135445 [...] Today we introduce an icon for Optimized Code pattern: [...] […] Today we introduce an icon for Optimized Code pattern: […]

]]> https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-83534 Crash Dump Analysis » Blog Archive » Virtualized process, incorrect stack trace, stack trace collection, multiple exceptions, optimized code and C++ exception: pattern cooperation Wed, 08 Jul 2009 19:53:59 +0000 https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-83534 [...] a pointer to an exception pointers structure is NULL (probably because of optimized code) and we cannot use .exptr command. However we can still use a technique described in Hidden [...] […] a pointer to an exception pointers structure is NULL (probably because of optimized code) and we cannot use .exptr command. However we can still use a technique described in Hidden […]

]]> https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-77372 David Richter Tue, 02 Jun 2009 04:49:04 +0000 https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-77372 Excellent site. I have found that third party device drivers that have not passed though MS driver testing are culprit even though the stack might not point to them, or the lm command. The driver could have allocated a buffer and made a system call (which caused the crash). It is likely, however, that the driver passed it some erroneous data. As well all know, applications crash when a thread of execution accesses a block of memory it does not own, or it does own but corrupts its state. I saw a big improvement with the introduction of Vista SP1, yet I will still find my system to hang should I fill up with third party downloads. I find a quickened system when I use driver verifier. Oh, and you have an outstanding site. Excellent site. I have found that third party device drivers that have not passed though MS driver testing are culprit even though the stack might not point to them, or the lm command. The driver could have allocated a buffer and made a system call (which caused the crash). It is likely, however, that the driver passed it some erroneous data. As well all know, applications crash when a thread of execution accesses a block of memory it does not own, or it does own but corrupts its state. I saw a big improvement with the introduction of Vista SP1, yet I will still find my system to hang should I fill up with third party downloads. I find a quickened system when I use driver verifier. Oh, and you have an outstanding site.

]]> https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-71878 Software Generalist » Blog Archive » Reading Notebook: 22-Apr-09 Wed, 22 Apr 2009 16:51:38 +0000 https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-71878 [...] safe register association with arguments at the beginning of a function (p. 164) - See my Optimized Code pattern: http://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/ [...] […] safe register association with arguments at the beginning of a function (p. 164) - See my Optimized Code pattern: http://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/ […]

]]> https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-43017 !analyze -v : Crash Dump Analysis Pattern (Part 5) Wed, 17 Sep 2008 08:55:46 +0000 https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-43017 [...] http://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/ [...] […] http://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/ […]

]]> https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-18508 Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 50) Fri, 15 Feb 2008 15:28:48 +0000 https://www.dumpanalysis.org/blog/index.php/2006/12/15/crash-dump-analysis-patterns-part-5/#comment-18508 [...] I call this pattern as False Function Parameters where double checks and knowledge of calling conventions are required. Sometimes this pattern is a consequence of another pattern that I previously called Optimized Code. [...] […] I call this pattern as False Function Parameters where double checks and knowledge of calling conventions are required. Sometimes this pattern is a consequence of another pattern that I previously called Optimized Code. […]

]]>