diff options
| author | Ulf Hermann <[email protected]> | 2017-02-10 15:19:40 +0100 |
|---|---|---|
| committer | Mark Wielaard <[email protected]> | 2017-05-02 15:25:36 +0200 |
| commit | a55df2c16721010bf1a9900038c0736bd578c913 (patch) | |
| tree | 3f103388c06b09b28b47fb67896b965426f2ebb8 /tests/backtrace.x86_64.fp.exec.bz2 | |
| parent | 5e6615076a8ad5fad5c70b4ea266042ed7c44d55 (diff) | |
Add frame pointer unwinding as fallback on x86_64
If we don't find any debug information for a given frame, we usually
cannot unwind any further. However, the binary in question might have
been compiled with frame pointers, in which case we can look up the
well known frame pointer locations in the stack snapshot and use them
to bridge the frames without debug information.
The "unwind" hook is the right place for this as it is so far only
used on s390 and called only after trying to unwind with debug
information.
Signed-off-by: Ulf Hermann <[email protected]>
Diffstat (limited to 'tests/backtrace.x86_64.fp.exec.bz2')
| -rw-r--r-- | tests/backtrace.x86_64.fp.exec.bz2 | bin | 0 -> 434645 bytes |
1 files changed, 0 insertions, 0 deletions
diff --git a/tests/backtrace.x86_64.fp.exec.bz2 b/tests/backtrace.x86_64.fp.exec.bz2 Binary files differnew file mode 100644 index 00000000..06958452 --- /dev/null +++ b/tests/backtrace.x86_64.fp.exec.bz2 |