https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Thu, 07 May 2026 05:35:10 +0000 http://wordpress.org/?v=2.3.3 https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-155370 Crash Dump Analysis » Blog Archive » Ana-Trace-Log-Lyzer Wed, 02 Jun 2010 01:30:19 +0000 https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-155370 [...] Statement Density and Current [...] […] Statement Density and Current […]

]]> https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-151449 Crash Dump Analysis » Blog Archive » Trace Analysis Patterns (Part 23) Tue, 11 May 2010 06:24:50 +0000 https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-151449 [...] Statement Density and Current [...] […] Statement Density and Current […]

]]> https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-124269 Crash Dump Analysis » Blog Archive » Trace Analysis Patterns (Part 15) Sat, 13 Feb 2010 00:56:55 +0000 https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-124269 [...] When looking at software traces and doing either a search for or just scrolling certain messages have our attention immediately. We call them Significant Events and hence the name of this pattern, Significant Event. It could be a recorded exception or an error, a basic fact, a trace message from vocabulary index, or just any trace statement that marks the start of some activity we want to explore in depth, for example, a certain DLL is attached to the process, a coupled process is started or a function is called. The start of a trace and the end of it are trivial significant events and are used in deciding whether the trace is circular, in determining the trace recording interval or its average statement current. [...] […] When looking at software traces and doing either a search for or just scrolling certain messages have our attention immediately. We call them Significant Events and hence the name of this pattern, Significant Event. It could be a recorded exception or an error, a basic fact, a trace message from vocabulary index, or just any trace statement that marks the start of some activity we want to explore in depth, for example, a certain DLL is attached to the process, a coupled process is started or a function is called. The start of a trace and the end of it are trivial significant events and are used in deciding whether the trace is circular, in determining the trace recording interval or its average statement current. […]

]]> https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-105002 Crash Dump Analysis » Blog Archive » Trace Analysis Patterns (Part 12) Tue, 17 Nov 2009 16:03:21 +0000 https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-105002 [...] with thousands and millions of messages (trace statements) we can see regions of activity where statement current (Jm, msg/s) is much higher than in surrounding temporal regions. Hence the name of this pattern, [...] […] with thousands and millions of messages (trace statements) we can see regions of activity where statement current (Jm, msg/s) is much higher than in surrounding temporal regions. Hence the name of this pattern, […]

]]> https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-98724 Crash Dump Analysis » Blog Archive » Statement current, coupled processes, wait chain, spiking thread, hidden exception, and not my version: memory dump and trace analysis pattern cooperation Mon, 12 Oct 2009 19:11:17 +0000 https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-98724 [...] when the problem happens again. The trace revealed the following message with exceptionally high statement current of 72,118 msg/s (and also superdense - no other types of trace statements were found [...] […] when the problem happens again. The trace revealed the following message with exceptionally high statement current of 72,118 msg/s (and also superdense - no other types of trace statements were found […]

]]> https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-91662 Crash Dump Analysis » Blog Archive » Trace Analysis Patterns (Part 10) Tue, 01 Sep 2009 15:32:32 +0000 https://www.dumpanalysis.org/blog/index.php/2009/07/22/trace-analysis-patterns-part-5/#comment-91662 [...] distribution differs greatly in both size and content. Despite the same tracing time, 15 seconds, statement current is 155 msg/s for working and 388 msg/s for non-working [...] […] distribution differs greatly in both size and content. Despite the same tracing time, 15 seconds, statement current is 155 msg/s for working and 388 msg/s for non-working […]

]]>