Simple iterate over a list of processes (randomized order) and send SIGKILL or
SIGTERM to the processes. Which signal is send is configured and must be decided
by the user. Not every application react properly to SIGTERM. Other applications
are required to do so. If compiled with -fsanitize=leak and SIGTERM frees all memory
after this 'Robustness Tester' should catch such errors.
This programs requires no external library, just because getting third party packages cross compiled for embedded platforms is somehow tricky (no psutils). This script uses ctype, if some exception occur - please read the comments in the source code above the exception.
This programs heavily kills (sigterm, sigkill) and ptraces to processes. Due to
the mature of how Linux works (better UNIX), using the PID as an process
identificator is not clean, rather it is racy to some degree. I wait for a new
linux syscall where this gap is closed: pidfd_open(). But until this is not
yet mainline, it is the only choice.
$ $EDITOR ./robustness-tester.py
$ sudo systemd-run ./robustness-tester.py
Running as unit: run-r6736d845ae3b414899f47fdbecd08824.service
# check if running correctly:
$ sudo systemctl status run-r6736d845ae3b414899f47fdbecd08824.service
Why via systemd-run? Because the output of all other applications will be in
the journal - in one journal and you can correlate them easily.
$ sudo journalctl -f -n 100
$ sudo systemctl stop run-r6736d845ae3b414899f47fdbecd08824.service