annotate: fix how snprintf() is handled
commit994c24afcfcf62f88e5d1b6e62e13fadb858eeae
authorDan Carpenter <dan.carpenter@oracle.com>
Thu, 19 Nov 2020 12:12:41 +0000 (19 15:12 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Thu, 19 Nov 2020 12:12:41 +0000 (19 15:12 +0300)
tree7bce2da5766dd5b713689b61644c487bfa72e258
parent7938912d447f2cad1c4072b316c4e4168947d890
annotate: fix how snprintf() is handled

I don't remember if this is a real bug or a theoretical bug.  If we can't
determine what the return value is then this should return 0/false but
originally it always returned true.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
smatch_annotate.c