- 06 Jun, 2016 4 commits
-
-
Cedric Roux authored
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.
-
Cedric Roux authored
and also start to use the PHY textview
-
Cedric Roux authored
-
Cedric Roux authored
always a good idea to crash in unknown situations...
-
- 05 Jun, 2016 6 commits
-
-
Cedric Roux authored
enb.c will then try to reconnect.
-
Cedric Roux authored
-
Cedric Roux authored
it may legitimately happen when the tracee is ctrl+c'ed. Let's print something though because read may fail for other reasons. Why not?
-
Cedric Roux authored
write() on a socket with the other end closed throws a SIGPIPE. Let's ignore this signal. write() will return an error anyway...
-
Cedric Roux authored
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...
-
Cedric Roux authored
The application (enb.c basically) will now monitor the socket and reconnect if it dies. See following commits.
-
- 04 Jun, 2016 3 commits
-
-
Cedric Roux authored
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).
-
Cedric Roux authored
-
Cedric Roux authored
-
- 02 Jun, 2016 2 commits
-
-
Cedric Roux authored
The unit simulators may still need some checks.
-
Cedric Roux authored
(the T macro is then undefined)
-
- 01 Jun, 2016 4 commits
-
-
Cedric Roux authored
if a read from the remote tracer's socket fails, let's smash the socket and wait for another remote tracer
-
Cedric Roux authored
it's buggy. Next commit to fix it. The problem is if the tracer exits while sending a message. The local tracer will not get it full and will throw garbage to the T in the tracee, leading to some bad things...
-
Cedric Roux authored
-
Cedric Roux authored
plus some cleanup here and there
-
- 31 May, 2016 8 commits
-
-
Cedric Roux authored
-
Cedric Roux authored
get rid of forward.c, make everything static inside local.c
-
Cedric Roux authored
remove forward stuff from defs.h remove defs.h from local.c and forward.c
-
Cedric Roux authored
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.
-
Cedric Roux authored
-
Cedric Roux authored
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
-
Cedric Roux authored
get rid of T_send(), no use anymore
-
Cedric Roux authored
The T only works when it's TRUE, the version without shared memory is not supported anymore.
-
- 27 May, 2016 8 commits
-
-
Cedric Roux authored
can be deactivated on the command line or in the gui
-
Cedric Roux authored
-
Cedric Roux authored
-
Cedric Roux authored
-
Cedric Roux authored
-
Cedric Roux authored
-
Cedric Roux authored
-
Cedric Roux authored
-
- 25 May, 2016 5 commits
-
-
Cedric Roux authored
-
Cedric Roux authored
- adding T macros here and there - modify the T_messages.txt - modify enb.c to trace them in the RRC view
-
Cedric Roux authored
plus add rrc connection setup complete tracing
-
Cedric Roux authored
-
Cedric Roux authored
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...)
-