this may be removed at some point, it's very brutal. But when you
write some code, it may happen (it "may"!!) that *sometimes* the
code does not work and crashes. In thoses cases I prefer the
local tracer (or the tracee) to go away immediately without even
thinking about it maybe still running in the background.
In case of monitoring (as opposed to debugging) maybe it's preferable
to let the process live its life as it wants.
Time will tell.
first step: let the tracee connect before the remote tracer
and let's have a "no wait" mode where the local tracer starts
the tracee before the remote tracer is connected
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...)
Cedric Roux