public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] libctf: fix uninitialized variables in testsuite
@ 2024-03-11 17:18 Nick Alcock
  0 siblings, 0 replies; only message in thread
From: Nick Alcock @ 2024-03-11 17:18 UTC (permalink / raw)
  To: bfd-cvs, gdb-cvs

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9b9e262994636841de04b433413e8987b16fcbaa

commit 9b9e262994636841de04b433413e8987b16fcbaa
Author: Nick Alcock <nick.alcock@oracle.com>
Date:   Tue Jan 30 14:18:54 2024 +0000

    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.

Diff:
---
 libctf/testsuite/libctf-writable/libctf-errors.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libctf/testsuite/libctf-writable/libctf-errors.c b/libctf/testsuite/libctf-writable/libctf-errors.c
index 71f8268cfad..2790b608396 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;

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-03-11 17:18 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-11 17:18 [binutils-gdb] libctf: fix uninitialized variables in testsuite Nick Alcock

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).