VTY Crash due an assumption we are breaking

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Wed Aug 11 17:40:14 UTC 2010


Hi Zecke,

On Wed, Aug 11, 2010 at 04:39:44AM +0800, Holger Hans Peter Freyther wrote:

> we also have a similiar issue with the subscriber_put in the exit function...
> the only fix I can think of is to move every node that frees data before the
> CONFIG_NODE so we will not have the "auto fixup" code of VTY.

sounds fair to me.  The auto-fixup code needs to be there for config file
parsing, where we never really know when to return from a sub-level
back to its parent, as there is no explicit 'exit' in the config file.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)




More information about the OpenBSC mailing list