Nick Alcock 9b9e262994 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.		2024-03-11 17:16:12 +00:00
..
doc
testsuite	libctf: fix uninitialized variables in testsuite	2024-03-11 17:16:12 +00:00
.gitignore
aclocal.m4
ChangeLog
ChangeLog-2020
config.h.in
configure
configure.ac
ctf-archive.c
ctf-create.c
ctf-decl.c
ctf-decls.h
ctf-dedup.c
ctf-dump.c
ctf-endian.h
ctf-error.c
ctf-hash.c
ctf-impl.h
ctf-inlines.h
ctf-intl.h
ctf-labels.c
ctf-link.c
ctf-lookup.c
ctf-open-bfd.c
ctf-open.c
ctf-qsort_r.c
ctf-serialize.c
ctf-sha1.c
ctf-sha1.h
ctf-string.c
ctf-subr.c
ctf-types.c
ctf-util.c
elf.h
libctf.ver
Makefile.am
Makefile.in
NEWS
swap.h