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
..
error-propagation.c
error-propagation.lk
libctf-errors.c
libctf-errors.lk
parent-child-dtd-crash-lib.c
parent-child-dtd-enum.c
parent-child-dtd-enum.lk
parent-child-dtd-enumerator.c
parent-child-dtd-enumerator.lk
parent-child-dtd-member-encoded.c
parent-child-dtd-member-encoded.lk
parent-child-dtd-member-offset.c
parent-child-dtd-member-offset.lk
parent-child-dtd-set-array.c
parent-child-dtd-set-array.lk
parent-child-dtd-struct.c
parent-child-dtd-struct.lk
parent-child-dtd-union.c
parent-child-dtd-union.lk
pptrtab-writable-page-deep-lookup.c
pptrtab-writable-page-deep-lookup.lk
pptrtab.c
pptrtab.lk
reserialize-strtab-corruption.c
reserialize-strtab-corruption.lk
symtypetab-nonlinker-writeout.c
symtypetab-nonlinker-writeout.lk
writable.exp