libctf: make ctf_bfdopen_ctfsect a debugger entry point

This makes it possible to use LIBCTF_DEBUG to debug things that happen
before the ctf_bfdopen_internal call that ctf_bfdopen_ctfsect eventually
thunks down to (symtab/strtab lookup, archive opening, etc).

This is not important for ctf_open callers, since ctf_fdopen already
calls libctf_init_debug, but ctf_bfdopen_ctfsect is a public entry point
that can be called directly (e.g. objdump and readelf both do so).

libctf/ChangeLog
2021-03-25  Nick Alcock  <nick.alcock@oracle.com>

	* ctf-open-bfd.c (ctf_bfdopen_ctfsect): Initialize debugging.
This commit is contained in:
Nick Alcock 2021-03-25 16:32:46 +00:00
parent 86f64bf43f
commit 5226ef6113
2 changed files with 6 additions and 0 deletions

View File

@ -1,3 +1,7 @@
2021-03-25 Nick Alcock <nick.alcock@oracle.com>
* ctf-open-bfd.c (ctf_bfdopen_ctfsect): Initialize debugging.
2021-03-25 Nick Alcock <nick.alcock@oracle.com>
PR libctf/27628

View File

@ -99,6 +99,8 @@ ctf_bfdopen_ctfsect (struct bfd *abfd _libctf_unused_,
char *strtab_alloc = NULL;
int symsect_endianness = -1;
libctf_init_debug();
#ifdef HAVE_BFD_ELF
ctf_sect_t symsect, strsect;
Elf_Internal_Shdr *symhdr;