-(4) create a event rate graphical view : Will be useful in conjonction with the
- filter.<br>
- # <A HREF="mailto:Parisa Heidari <parisa.heidari@polymtl.ca>">Parisa Heidari</A><br>
-(7) create an analysis of function time (like a precise gprof)<br>
- -> with gcc -f inline-functions<br>
-(7) Create a hardware counter viewer (low cost rate counters : L1 cache miss, page faults, interrupts...).<br>
+(3) Make LTTV aware of type formats (visual separators) defined in the XML
+file.<br>
+(3) Use a per architecture enumeration for traps.<br>
+(4) Add event specific fields support to filter.<br>
+(4) Add a periodic event interval view. (useful to verify event periodicity)<br>
+(4) create a graphical per cpu activity view.<br>
+(5) Add Python scripting hooks.<br>
+(5) Flight recorder : start lttd automatically upon GUI trace control stop.<br>
+(5) Automatically detect traces with too much processes and disable faulty operations.<br>
+(5) Event sequence detector (inspired from regular expressions).<br>
+(7) Create a hardware counter viewer (low cost rate counters : L1 cache miss,
+page faults, interrupts...). This will be a generalisation of the event rate
+view into a view of the evolution of a user definable event field.<br>