diff options
| author | Carmelo Amoroso <carmelo.amoroso@st.com> | 2012-01-13 12:27:29 +0100 |
|---|---|---|
| committer | Carmelo Amoroso <carmelo.amoroso@st.com> | 2012-01-13 12:27:29 +0100 |
| commit | 93a11d8bb29423727cdd71c12b6ae8accc21997b (patch) | |
| tree | 402d977dc6f1edae9bc024e8ed5de4762f01c713 /libubacktrace/backtrace.c | |
| parent | 4c9b7f3c21ff21c199e54bfad2fdf3445fa4573d (diff) | |
libubacktrace: use -asynchronous-funwind-tables rather than -funwind-tables
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>
Diffstat (limited to 'libubacktrace/backtrace.c')
| -rw-r--r-- | libubacktrace/backtrace.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/libubacktrace/backtrace.c b/libubacktrace/backtrace.c index e5f513040..205a0a0ce 100644 --- a/libubacktrace/backtrace.c +++ b/libubacktrace/backtrace.c @@ -2,7 +2,7 @@ * Perform stack unwinding by using the _Unwind_Backtrace. * * User application that wants to use backtrace needs to be - * compiled with -funwind-tables option and -rdynamic to get full + * compiled with -fasynchronous-unwind-tables option and -rdynamic to get full * symbols printed. * * Copyright (C) 2009, 2010 STMicroelectronics Ltd. |