Open clopez opened 11 months ago
Does it help if you run gcc -c -g testbt.c -o testbt.o
? I added the -g
option.
I just tested to add the -g
option and unfortunately it doesn't help.
This is the info about the testbt
binary that gets built, just in case is useful.
$ file testbt
testbt: ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=ff2046b946518a75d05e88704a33c7429a1d991d, for GNU/Linux 3.2.0, with debug_info, not stripped
$ ldd testbt
linux-vdso.so.1 (0xf7907000)
libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xf7887000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xf7788000)
/lib/ld-linux-armhf.so.3 (0xf78df000)
When I try to use libbacktrace on Linux 32-bits I get an empty backtrace.
See the following example program: http://ix.io/4Jf4
Build it like:
And then execute it.
On Debian/arm64 (64-bits) you get this:
So far, so good
However, on Debian/armhf (ARM 32-bits) you get this:
So it prints nothing.
Some info about my test environment in case it is useful:
make check
and it passes fine (also it passes on ARM-32 bits)