mirror of https://gerrit.osmocom.org/libosmocore
ea6f519ff8
We must explicitly check the return value of osmo_log_vty2tgt(), or may run into a segfault. I wasn't aware of this and introduced numerous such cases in I36f17c131cc70ce5a1aef62fd9693097de230cd4. Reproduce: on the VTY, do not issue 'logging enable', invoke 'logging level force-all LEVEL' first. Show in logging_vty_test.vty that this situation is now again amended by telling the user that logging was not enabled. Related: OS#3611 Change-Id: Id11702d1801d6654ca5e5a51b597a0d802e2e8dd |
||
---|---|---|
.. | ||
logging_test.c | ||
logging_test.err | ||
logging_test.ok | ||
logging_vty_test.c | ||
logging_vty_test.vty |