summaryrefslogtreecommitdiff
path: root/libubacktrace/backtrace.c
AgeCommit message (Collapse)Author
2012-01-13libubacktrace: use -asynchronous-funwind-tables rather than -funwind-tablesCarmelo Amoroso
From gcc documentation, we can read: " ... -fasynchronous-unwind-tables Generate unwind table in dwarf2 format, if supported by target machine. The table is exact at each instruction boundary, so it can be used for stack unwinding from asynchronous events (such as debugger or garbage collector) ..." So it seems better rather than using -funwind-tables (glibc seems to prefer -fasynchronous-unwind-tables). Signed-off-by: Carmelo Amoroso <carmelo.amoroso@st.com> Acked-by: Mike Frysinger <vapier@gentoo.org>
2011-12-22libubacktrace: use -funwind-tables rather than -fexecptionsCarmelo Amoroso
For backtrace to work is enough to use -funwind-tables instead of -fexceptions. Signed-off-by: Carmelo Amoroso <carmelo.amoroso@st.com>
2011-04-22libubacktrace: generic implementation based dwarfCarmelo Amoroso
Use the initial implementation for SH4 based on dwarf for all archs. Indeed there are not obvious reason for which it should not work in general. Signed-off-by: Carmelo Amoroso <carmelo.amoroso@st.com>
2010-09-15libubacktrace: Provide uClibc with backtrace functionsSalvatore Cro
A new shared object, libubacktrace.so.0 is added to uClibc to provide backtrace functions to support application self-debugging. This set of functions requires to dynamically load libgcc_s.so so they need to call dlopen/dlsym that are provided by libdl. For this reason they cannot be included into libc.so.0 but are provided by a new library. User application that wants to use backtrace needs to be compiled with -fexceptions option and -rdynamic to get full symbols printed and must be linked against libubacktrace.so Signed-off-by: Carmelo Amoroso <carmelo.amoroso@st.com>