[Ltrace-devel] ltrace on ppc64

Andreas Schwab schwab at linux-m68k.org
Fri Jul 17 16:37:31 UTC 2015


The ltrace.main/dwarf test produces this output on ppc64:

static .opd translation of 0x3fffb7fad190: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fad1b8: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fad280: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fad330: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fad600: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fad75c: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fad798: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fad7c8: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fadc30: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fae580: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fae5a0: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fae5e8: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fbee08: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fbee10: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fbee18: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fbee20: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fbf000: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fbf1d0: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fbf208: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fbf310: no error
couldn't translate address of @libdwarftest.so: Success
static .opd translation of 0x3fffb7fbee18: no error
couldn't translate address of __JCR_LIST__ at libdwarftest.so: Success
static .opd translation of 0x3fffb7fbf310: no error
couldn't translate address of completed.8411 at libdwarftest.so: Success
static .opd translation of 0x3fffb7fbee10: no error
couldn't translate address of __do_global_dtors_aux_fini_array_entry at libdwarftest.so: Success
static .opd translation of 0x3fffb7fbee08: no error
couldn't translate address of __frame_dummy_init_array_entry at libdwarftest.so: Success
static .opd translation of 0x3fffb7fae6d0: no error
couldn't translate address of __FRAME_END__ at libdwarftest.so: Success
static .opd translation of 0x3fffb7fbee18: no error
couldn't translate address of __JCR_END__ at libdwarftest.so: Success
static .opd translation of 0x3fffb7fbf000: no error
couldn't translate address of __dso_handle at libdwarftest.so: Success
static .opd translation of 0x3fffb7fbee20: no error
couldn't translate address of _DYNAMIC at libdwarftest.so: Success
static .opd translation of 0x3fffb7fbf208: no error
couldn't translate address of _edata at libdwarftest.so: Success
static .opd translation of 0x3fffb7fbf318: no error
couldn't translate address of _end at libdwarftest.so: Success
static .opd translation of 0x3fffb7fbf208: no error
couldn't translate address of __bss_start at libdwarftest.so: Success

The first few errors come from section symbols, the rest are STT_OBJECT
symbols.  Shouldn't populate_this_symtab generally ignore section
symbols?  Should it exempt STT_OBJECT symbols from going through
arch_translate_address?

Andreas.

-- 
Andreas Schwab, schwab at linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



More information about the Ltrace-devel mailing list