Regression tests for ctf reader: Avoid duplicating files
Guillermo Martinez
guillermo.e.martinez@oracle.com
Wed Nov 3 22:41:42 GMT 2021
Hello,
I'm working in the implementation of regression tests for ctf reader
(tests/test-read-ctf.cc), it's very similar to test-read-dwarf.cc, so
they have some C and header source files that are common among
them, e.g:
tests/data/test-read-ctf/PR27700/include-dir/priv.h
tests/data/test-read-ctf/PR27700/include-dir/pub.h
tests/data/test-read-ctf/PR27700/pub-incdir/inc.h
tests/data/test-read-ctf/PR27700/test-PR27700.c
tests/data/test-read-ctf/test-PR26568-1.c
tests/data/test-read-ctf/test-PR26568-2.c
So, we're planning move those common source file to:
tests/data/test-read-common/
But we still need *two different* binary files with the debugging
information: DWARF (-gdwarf) and CTF (-gctf), that they would
need to be recompiled. The current implementation to test ctf reader
use binary files previously compiled, so there is one file for
each binary format:
tests/data/test-read-*ctf*/test-PR26568-1.o
...
tests/data/test-read-*dwarf*/test-PR26568-1.o
So, Are you agree with this approach?
We are looking for the way to avoid duplicating files :-)
Thanks in advanced for your comments!
Sincerely,
Guillermo
More information about the Libabigail
mailing list