Trace Analysis Patterns (Part 41)
UI Message pattern is very useful for troubleshooting system-wide issues because we can map visual behaviour to various activity regions and consider such messages as significant events.
# Module PID TID Time Message
[...]
2782 ModuleA 2124 5648 10:58:03.356 CreateWindow: Title "..." Class "..."
[...]
3512 ModuleA 2124 5648 10:58:08.154 Menu command: Save Data
[...]
3583 ModuleA 2124 5648 10:58:08.155 CreateWindow: Title "Save As" Class "Dialog"
[... Data update and replication related messages ...]
4483 ModuleA 2124 5648 10:58:12.342 DestroyWindow: Title "Save As" Class "Dialog"
[...]
By filtering the emitting module we can create an adjoint thread:
# Module PID TID Time Message
[...]
2782 ModuleA 2124 5648 10:58:03.356 CreateWindow: Title "..." Class "..."
3512 ModuleA 2124 5648 10:58:08.154 Menu command: Save Data
3583 ModuleA 2124 5648 10:58:08.155 CreateWindow: Title "Save As" Class "Dialog"
4483 ModuleA 2124 5648 10:58:12.342 DestroyWindow: Title "Save As" Class "Dialog"
[...]
- Dmitry Vostokov @ DumpAnalysis.org + TraceAnalysis.org -
July 29th, 2011 at 8:04 am
Hi Dmitry,
which tool / command is this output from?
thx, Juergen
July 30th, 2011 at 9:37 pm
This is fictional output from CDFAnalyzer but the idea comes from real CDF traces where certain Citrix modules emit GUI-related messages
August 3rd, 2011 at 7:16 am
Thanks, - I googled CDF and found that it means either “Citrix Diagnostic Facility” or “Common Diagnostic Facility” therefore I assume that this Traces are Citrix specific.
Is there a similar thing/tool for doing/getting such traces from normal normal/locally running applications?
August 3rd, 2011 at 2:13 pm
Not really Citrix specific - CDF is a version of Microsoft ETW (Event Tracing for Windows) that is now part of every Windows version. My point was that an application can include such trace messages. However if you just need to see window messages that are received by Windows app you can use MessageHistory: http://support.citrix.com/article/CTX111068