The T has 2 processes: the tracee and the local tracer
if the tracee dies (segfault or whatever) the tracee
may still be running.

So there is a third process that monitors those two others
and kill everything when one dies.

The problem is that this third process has to be the parent
of the two others. That makes debugging the tracee with gdb
impossible. This new option disables the third monitor process.

we have to free memory in any case...

git status was way too noisy

ctrl+c did not work when the program was not connected yet.
It also didn't work if no event was received.

And it's sent at each connection attempt.
Before it was sent only once to the first tracer.
Plus there was a bug (length:(len) should have been length:(send_size)).

needed because of the following commit

stuff put in there is of lower quality / coding standard / whatever
and serves as example to do quick debugging taks using the T
infrastructure

the current version is very specific to PUSCH IQ data, where the
input buffer has a special format

to be rewritten cleanly at some point

XY_LOOP_MODE: replace old points with new ones, using the maximum size
              of the view
XY_FORCE_MODE: append_forced sets those and only those points
               and we crash if we pass too much points

to be used in conjunction with another tracer
so conceptually it's more a tracee than a tracer

very basic, to be refined, find a nice way to display (plot? text?)
protocol data movement

to be refined, it's rough

3 pixels wide look better than 1

- update T_messages.txt
- update call sites of the T for thoses traces

more readable, still not satisfying though

events are accepted by the logger if the filter accepts them
the filter is optional (no filter means to accept all events)

this is like timeview but the plotting is done at frame/subframe
resolution of a given reference clock signal, let's say.

The realtime information of the events is not used. It's all
logical.

It will be used to log harq processes for the moment.