[prev in list] [next in list] [prev in thread] [next in thread] 

List:       buildroot
Subject:    [Buildroot] backtrace()  depth
From:       Peter_Kümmel <syntheticpp () gmx ! net>
Date:       2013-09-10 19:18:38
Message-ID: 522F708E.2070004 () gmx ! net
[Download RAW message or body]

I've a question about the depth of a backtrace.

I've configured uClibc/Buildroot to build libubacktrace-0.9.33.2.so
via the standard Buildroot menuconfigs:
Buildroot 2013.02, GCC 4.7.2 by Buildroot, uClibc-0.9.33

When I call backtrace() on a segfault, I only see the function
where the segfault is produced, and not much more (only /lib/libc.so.0,
and two more addresses). The function name could be demanded correctly,
so I assume the compiler flags are ok (-rdynamic).

The segfault is not in the main thread
(overall 4 threads, /lib/libpthread-0.9.33.2.so)
And the bt looks equal for debug and release builds.

A build with crosstool-ng and eglibc produces the same bad backtrace.

Is there a way to get a more complete backtrace?

Many thanks,
Peter
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
[prev in list] [next in list] [prev in thread] [next in thread]