New Defects reported by Coverity Scan for Osmocom

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 osmocom.org
Wed Aug 26 18:47:12 UTC 2020


On Wed, Aug 26, 2020 at 02:23:03PM +0200, nhofmeyr at sysmocom.de wrote:

> I'd like to let you guys know that I intentionally don't check the return value
> here. This is only for logging the mobile identity, and if decoding fails, the
> logging should just show "NONE".

AFAIR, there are ways how you can annotate the code in a way to avoid coverity raising it.

There should be something like //coverity[] but some people claim there is also the option of
casting the return value to (void):
	https://stackoverflow.com/questions/5073164/coverity-prevent-how-to-handle-checked-return-warning-when-i-deliberately-don

-- 
- Harald Welte <laforge at osmocom.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