../../../src/server/ruleset.c:2010:26: warning: Array access (from variable 'vlist_raise') results in a null pointer dereference [core.NullDereference]
(vlist_raise[i] < 0), vlist_raise[i] = 0);
../../../src/server/ruleset.c:1998:7: note: expanded from macro 'rs_sanity_veteran'
if (_condition) {
---
That it warns only about vlist_raise, and not about the other arrays hints that the problem is with the compat handling in S3_1 (update from 3.0 to 3.1). I don't see real bug there, as 'count_raise' will be set to zero by secfile_lookup_int_vec() when ever it returns NULL. Compiler just doesn't know it, but seeing that check against NULL only in compat mode makes it think that NULL might live on in non-compat mode.
S3_1:
../../../src/server/ruleset.c:2010:26: warning: Array access (from variable 'vlist_raise') results in a null pointer dereference [core.NullDereference]
(vlist_raise[i] < 0), vlist_raise[i] = 0);
../../../src/server/ruleset.c:1998:7: note: expanded from macro 'rs_sanity_veteran'
if (_condition) {
That it warns only about vlist_raise, and not about the other arrays hints that the problem is with the compat handling in S3_1 (update from 3.0 to 3.1). I don't see real bug there, as 'count_raise' will be set to zero by secfile_lookup_int_vec() when ever it returns NULL. Compiler just doesn't know it, but seeing that check against NULL only in compat mode makes it think that NULL might live on in non-compat mode.