https://www.dumpanalysis.org/blog/index.php/2010/04/08/trace-analysis-patterns-part-20/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Wed, 06 May 2026 15:04:47 +0000 http://wordpress.org/?v=2.3.3 https://www.dumpanalysis.org/blog/index.php/2010/04/08/trace-analysis-patterns-part-20/#comment-194947 Crash Dump Analysis » Blog Archive » Trace Analysis Patterns (Part 31) Wed, 20 Oct 2010 16:27:00 +0000 https://www.dumpanalysis.org/blog/index.php/2010/04/08/trace-analysis-patterns-part-20/#comment-194947 [...] Please not that it is also possible to have a periodization based on modules, functions and individual messages but it might be complicated because different threads can enter the same module or function and here other patterns more appropriate like Activity Region, Characteristic Message Block, Background and Foreground Components. [...] […] Please not that it is also possible to have a periodization based on modules, functions and individual messages but it might be complicated because different threads can enter the same module or function and here other patterns more appropriate like Activity Region, Characteristic Message Block, Background and Foreground Components. […]

]]> https://www.dumpanalysis.org/blog/index.php/2010/04/08/trace-analysis-patterns-part-20/#comment-184015 Crash Dump Analysis » Blog Archive » Trace Analysis Patterns (Part 28) Mon, 13 Sep 2010 20:25:03 +0000 https://www.dumpanalysis.org/blog/index.php/2010/04/08/trace-analysis-patterns-part-20/#comment-184015 [...] Debugging Experts Magazine Online Often we see errors in software traces recorded during deviant software behavior (often called non-working software traces) and when we double check their presence in normal expected software behavior traces (often called working traces) we find them there too. This pattern is called False Positive Error. I have already mentioned when I introduced the first software trace analysis pattern Periodic Error. Here is an example from the real trace. In a non-working trace we found this error in an adjoint thread of a foreground component: [...] […] Debugging Experts Magazine Online Often we see errors in software traces recorded during deviant software behavior (often called non-working software traces) and when we double check their presence in normal expected software behavior traces (often called working traces) we find them there too. This pattern is called False Positive Error. I have already mentioned when I introduced the first software trace analysis pattern Periodic Error. Here is an example from the real trace. In a non-working trace we found this error in an adjoint thread of a foreground component: […]

]]>