stack: fix gdb.dwarf2/dw2-undefined-ret-addr.exp regression

Commit a038fa3e14a4 stack: check frame_unwind_caller_id adds a frame_id check to
frame_info and treats a missing frame_id as NOT_AVAILABLE_ERROR.  This causes a
regression in gdb.dwarf2/dw2-undefined-ret-addr.exp.

Treat a missing frame_id as OPTIMIZED_OUT_ERROR instead.

See also https://sourceware.org/ml/gdb-patches/2016-07/msg00273.html.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index fa491f0e325e88e6d79330dc09f80654012c114b..ea8fdd1918dc7c5b3ec24d633daa801c902c3801 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2016-10-06  Markus Metzger  <markus.t.metzger@intel.com>
+
+       * stack.c (frame_info): Call val_print_not_saved instead of
+       val_print_unavailable if frame_id check fails.
+
 2016-10-06  Pedro Alves  <palves@redhat.com>
 
        * jit.c (free_objfile_data): Delete the JIT breakpoint and clear

diff --git a/gdb/stack.c b/gdb/stack.c
index 3ce313800fb93dde567f3748cfcaada62c4f672d..c77bfc084e0d51f8fe5ddb85fc5b4523da133d67 100644 (file)
--- a/gdb/stack.c
+++ b/gdb/stack.c
@@ -1531,7 +1531,7 @@ frame_info (char *addr_exp, int from_tty)
   printf_filtered ("saved %s = ", pc_regname);
 
   if (!frame_id_p (frame_unwind_caller_id (fi)))
-    val_print_unavailable (gdb_stdout);
+    val_print_not_saved (gdb_stdout);
   else
     {
       TRY