Some of our source files are inherited from other sources, particularly
for microcontroller firmware projects. We cannot assume they're all
clean UTF-8. Let's ignore any decoder errors when verifying log
statements and value_string arrays.
Closes: OS#4334
Change-Id: I1e19f4bc6bee46481c6ea743e8334bd4485909be
If string eval encounters an uncovered parse error, it's useful to know which
file it happened in.
Change-Id: I5fe9a3bbdbfb8a995f24596bf09e70ca5bb3fe8a
This came up in
https://gerrit.osmocom.org/#/c/osmo-bsc/+/9671/6//COMMIT_MSG@36
The errors it finds in the current code base are numerous, and many are
intended LOGP .. LOGPC calls. It doesn't make sense to enforce this, but so far
this can be used manually.
Change-Id: Id79389f090a2fded7ff01dc7e3fe9774e7f22ca0