Bug #4149
open
we call osmo_identifier_valid()
for the FSM name and FSM instance, but we don't appear to use it for state or event names :(
- Category set to libosmocore
the initial patch breaks, as expected, a lot of existing FSMs, we need to resolve this first. Unfortunately there is also a problem with the debug log. Some FSMs are registered before the log is initialized. The logging framework will then exit with an assertion when the debug messages from the FSM registrations are printed. This needs to be resolved first to debug the problematic. See also: https://gerrit.osmocom.org/c/libosmocore/+/26950
Also available in: Atom
PDF