No, Phantom, Piecewise, Punctuated, Resume
Learn to identify and interpret complex software trace activities such as no activity, phantom activity, piecewise, punctuated, and resume patterns. This lesson helps you understand how these patterns reveal issues like missing threads, blocked processes, and message flow interruptions, improving your trace analysis skills.
We'll cover the following...
No activity
No activity is the limit of the discontinuity pattern. The absence of activity can be seen at a thread level or at a process level where it is similar to the missing component pattern. The difference from the latter pattern is that we know for certain that we selected our process modules for tracing but do not see any trace messages. Consider this example:
Only modules from the AppA process and modules from a coupled process (for example, ModuleB) were selected. However, we only see a reminder message from the coupled process (3124.4816: _ModuleB!WorkerThread_) and no messages for 21 seconds. Fortunately,
AppA process memory dump was saved during the tracing session:
Debug session time: Fri May 21 08:04:31.000 2010 (GMT+0)
We see two threads waiting for a ...