From 9b9e262994636841de04b433413e8987b16fcbaa Mon Sep 17 00:00:00 2001 From: Nick Alcock Date: Tue, 30 Jan 2024 14:18:54 +0000 Subject: libctf: fix uninitialized variables in testsuite Just because a path is an error path doesn't mean the program terminates there if you don't ask it to. And we don't want to -- but that means we need to initialize the variables that are missed if an error happens to *something*. Type ID 0 (unimplemented) will do: it'll induce further ECTF_BADID errors, but that's no bad thing. libctf/ChangeLog: * testsuite/libctf-writable/libctf-errors.c: Initialize variables. --- libctf/testsuite/libctf-writable/libctf-errors.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'libctf') diff --git a/libctf/testsuite/libctf-writable/libctf-errors.c b/libctf/testsuite/libctf-writable/libctf-errors.c index 71f8268..2790b60 100644 --- a/libctf/testsuite/libctf-writable/libctf-errors.c +++ b/libctf/testsuite/libctf-writable/libctf-errors.c @@ -12,7 +12,7 @@ main (int argc, char *argv[]) ctf_dict_t *fp; ctf_next_t *i = NULL; size_t boom = 0; - ctf_id_t itype, stype; + ctf_id_t itype = 0, stype = 0; ctf_encoding_t encoding = {0}; ctf_membinfo_t mi; ssize_t ret; -- cgit v1.1