Trace Analysis Patterns (Part 15)

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.

- Dmitry Vostokov @ + -

One Response to “Trace Analysis Patterns (Part 15)”

  1. Crash Dump Analysis » Blog Archive » Trace Analysis Patterns (Part 16) Says:

    […] Crash Dump Analysis Exploring Crash Dumps and Debugging Techniques on Windows Platforms « Trace Analysis Patterns (Part 15) […]

Leave a Reply

You must be logged in to post a comment.