-(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>
-(10) Add cancel button to LTTV filter GUI window.
+(4) Filter by target process.<br>
+(4) Compensate for time spent in probes in LTTV analysis.<br>
+(4) Add CPU, network, disk, memory usage histogram. [Per interval statistics]<br>
+(5) Add Python scripting hooks.<br>
+(5) Add GUI interface to take an hybrid trace.<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>
+<br>
+* TO FIX<br>
+(10) Add cancel button to LTTV filter GUI window.<br>
+(10) Sometimes, in the control flow view, a process with 0 creation time is
+created in addition to the real process itself. Seems to be caused by end of
+process life.<br>
+(10) Statistics do not take in account the time spent in the mode present at
+the beginning of the trace. Example : real time spent in system call on behalf
+of process 0.<br>