mirror of https://gerrit.osmocom.org/libosmocore
d28aa0c2f1
A separate ST_DESTROYING state originally helped with certain deallocation scenarios. But now that fsm.c avoids re-entering osmo_fsm_inst_term() twice and gracefully handles FSM instance deallocations for termination cascades, it is actually just as safe without a separate ST_DESTROYING state. ST_DESTROYING was used to flag deallocation and prevent entering osmo_fsm_inst_term() twice, which works only in a very limited range of scenarios. Remove ST_DESTROYING from fsm_dealloc_test.c to show that all tested scenarios still clean up gracefully. Change-Id: I05354e6cad9b82ba474fa50ffd41d481b3c697b4 |
||
---|---|---|
.. | ||
fsm_dealloc_test.c | ||
fsm_dealloc_test.err | ||
fsm_test.c | ||
fsm_test.err | ||
fsm_test.ok |