[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/.

Holger Hans Peter Freyther holger at freyther.de
Sun Mar 3 17:15:04 UTC 2013


On Sun, Mar 03, 2013 at 03:05:02PM +0000, Harald Welte wrote:

Hi,

> 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?

the current usage will be inside the regression/unit testing, e.g.
not having a dependency on the logging framework is quite nice to
have.

For osmo_backtrace and frpintf would be nice. I think the value of
osmo_backtrace will be a bit limited as we will have no symbol
name for the test function (but this could come from the fprintf).

cheers
	holger




More information about the OpenBSC mailing list