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

more readable, still not satisfying though

and also start to use the PHY textview

enb.c will then try to reconnect.

write() on a socket with the other end closed throws a SIGPIPE.
Let's ignore this signal. write() will return an error anyway...

fullread has been changed, so get_event too, and the callers also
for the moment the callers crash, enb.c will be a bit more clever,
the others to see...

The application (enb.c basically) will now monitor the socket
and reconnect if it dies. See following commits.

It was wrong.
Plus it is starting work so as to make enb.c not crashing if
the tracee goes away (maybe also textlog and vcd, but those are of
less importance).

The local tracer now waits for the remote tracer to connect,
that's no more the other way around.

All the remote tracers (textlog, enb, vcd) have also been converted.

can be deactivated on the command line or in the gui

- adding T macros here and there
- modify the T_messages.txt
- modify enb.c to trace them in the RRC view

plus add rrc connection setup complete tracing

as special events.

If we store all received events to a file, this dump is now
self-contained. Helps to analyze traces.

Some functions have also been factorized in the process, too much
duplication.

(Also tracer/Makefile was forgotten in previous commit, included
in this one...)

this calls clock_gettime for each active T macro, hopefully it
does not eat too much CPU

can be deactivated by commenting one line in T_defs.h

introducing generic "view" with two instantiations: stdout and textlist