[PATCH v2 0/4] Catch errors in get_prev_frame.

Andrew Burgess
2014-04-17T10:15:32Z

Seems I messed up the last patch series quite a bit, so this time I'm
trying out git send-email. Sorry for the noise, please let me know if it
still looks broken.

Nothing has changed here except, I hope, the patches should be well formed.

Thanks,
Andrew

Andrew Burgess (4):
New test for backtrace when the stack pointer is invalid (inaccessible).
Remove previous frame if an error occurs when computing frame id during unwind.
Deprecate frame_stop_reason_string.
Add a TRY_CATCH to get_prev_frame to better handle errors during unwind.

gdb/frame.c | 123 +-
gdb/frame.h | 11 +-
gdb/guile/scm-frame.c | 2 +-
gdb/python/py-frame.c | 2 +-
gdb/stack.c | 4 +-
.../gdb.arch/amd64-invalid-stack-middle.S | 1410 ++++++++++++++++++++
.../gdb.arch/amd64-invalid-stack-middle.c | 89 ++
.../gdb.arch/amd64-invalid-stack-middle.exp | 78 ++
gdb/testsuite/gdb.arch/amd64-invalid-stack-top.c | 73 +
gdb/testsuite/gdb.arch/amd64-invalid-stack-top.exp | 81 ++
gdb/unwind_stop_reasons.def | 5 +-
11 files changed, 1850 insertions(+), 28 deletions(-)
create mode 100644 gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.S
create mode 100644 gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.c
create mode 100644 gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.exp
create mode 100644 gdb/testsuite/gdb.arch/amd64-invalid-stack-top.c
create mode 100644 gdb/testsuite/gdb.arch/amd64-invalid-stack-top.exp

--
1.8.1.3