[PATCH] Changed assert to OSMO_ASSERT

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
Sun Mar 3 15:05:02 UTC 2013


Hi Katerina,

On Sun, Mar 03, 2013 at 10:36:52AM +0000, Katerina Barone-Adesi wrote:
> Rationale: zecke pointed out that the tests should unconditionally
> assert, regardless of debug settings.
> This uses the OSMO_ prefix as it's in the global namespace.

Two more ideas:

* since it is an error condition, fprintf(stderr).
* it might make sense to also write it to the osmocom logging,
  using LOGL_FATAL / DLGLOBAL
* while at it, we might also print a backtrace by means of
  osmo_backtrace().

What do you think?
-- 
- 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