I'm performing a UBsan run on GnuPG 2.2.15 and all of its dependencies. Everything was built with -fsanitize=undefined -fno-sanitize-recover. For Autotools projects the two flags get placed in CFLAGS, CXXFLAGS and LDFLAGS.
It looks like UBsan is producing some findings:
Checking TOFU trust model with ultimately trusted keys (issue2929). ("/home/build/gnupg-2.2.15/g10/gpg" --no-permission-warning --trust-model=tofu --quick-generate-key firstname.lastname@example.org) failed: gpg: keybox '/tmp/gpgscm-20190510T180345-run-tests-zh02be/pubring.kbx' created gpg: /tmp/gpgscm-20190510T180345-run-tests-zh02be/trustdb.gpg: trustdb created gpg: key CFAC68F08C2D9025 marked as ultimately trusted gpg: directory '/tmp/gpgscm-20190510T180345-run-tests-zh02be/openpgp-revocs.d' created armor.c:1159:11: runtime error: member access within null pointer of type 'struct string_list' 0: tests.scm:122: (throw (string-append (stringify what) " failed") (:stderr result)) 1: issue2929.scm:30: (call-check `(,@gpg --quick-generate-key email@example.com)) FAIL: tests/openpgp/issue2929.scm
Because -fno-sanitize-recover is used, abort() is called on a finding. It is needed because test frameworks often swallow the message *runtime error: ...* and the tester never gets to see it.