Hi all. We do have a problem with ltrace 0.7.3 tracing mips(el) binaries compiled with a mips plt enabled toolchain.
If I disable the "--with-mips-plt" gcc option during the toolchain build the ltrace debug output states that there are no relocations and tracing library calls do work. If I take binaries built with a mips plt enabled toolchain I do get different results: - tracing the busybox outputs: ... DEBUG: ltrace-elf.c:479: /proc/14300/exe 310 PLT relocations ... and I can see many library calls - tracing e.g. the openssl binary the output is (shortened): ... DEBUG: ltrace-elf.c:479: /proc/14261/exe 3 PLT relocations ... __uClibc_main(0x40b500, 2, 0x7fd05114, 0x4091a4 <unfinished ...> __register_frame_info(0x456dc0, 0x46a118, 0x7efefeff, 0x7efefcfc) = -1 ... __deregister_frame_info(0x456dc0, 1, 0, 75) = 0 +++ exited (status 0) +++ Is this a ltrace bug? What information can I provide to help to fix it? Or does our toolchain misbehave? I read some mails from Sedat in the archives about the PLT topic but nothing the helped me to solve this issue. You can find some more information in our Trac ticket (http://freetz.org/ticket/2326). Regards Oliver _______________________________________________ Ltrace-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/ltrace-devel
