Fix backtrace generation on Android/ARM/QNX
authorSimon Hausmann <simon.hausmann@digia.com>
Tue, 1 Oct 2013 14:34:21 +0000 (16:34 +0200)
committerThe Qt Project <gerrit-noreply@qt-project.org>
Thu, 3 Oct 2013 07:24:47 +0000 (09:24 +0200)
commit73dcd10dd060c6cc48f4def1c9cc39ca198acf6c
tree6f6918294bdd353f79af38aa64e2d31a471aa5b6
parent7d9780b6308e15dcd4adcb65d7b516666c285f54
Fix backtrace generation on Android/ARM/QNX

Use a GCC extension to the common C++ ABI's called _Unwind_Backtrace, which
generate backtraces if possible. Its direct use will ensure we use the
statically linked unwind, which knows about our unwind tables. This also helps
for the setup when libc doesn't have the glibc specific backtrace() function we
used previously. The unwinder on Mac OS X with clang also implements the same
extension.

Change-Id: I0b780590c10c16e50ec570f7da1efae2e64c46dd
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
src/qml/jsruntime/qv4stacktrace.cpp