Trace Analysis Patterns (Part 26)

Sometimes a software trace is truncated when the trace session was stopped prematurely, often when a problem didn’t manifest itself visually. We can diagnose such traces by their short time duration, missing anchor messages or components necessary for analysis. My favourite example is user session initialization in a Citrix terminal services environment when problem effects are visible only after the session is fully initialized and an application is launched but a truncated CDF trace only shows the launch of winlogon.exe despite the presence of a process creation trace provider or other components that record the process launch sequence and the trace itself lasts only a few seconds after that.

- Dmitry Vostokov @ + -

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

  1. Dmitry Vostokov Says:

    The other variant of a truncated trace is when its recording started later than necessary for analysis

Leave a Reply

You must be logged in to post a comment.