This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[commit] Require legacy_frame_p when "seriously old code"


Hello,

Without this it is impossible to update an architecture to implement the new frame unwind mechanism without simultaneously updating the architecture to use generic dummy frames. This at breaks the catch 22 making it possible to at least implement / test the new unwind code.

committed,
Andrew
2004-02-22  Andrew Cagney  <cagney@redhat.com>

	* frame-unwind.c (frame_unwind_find_by_frame): Add legacy_frame_p
	to predicates for "seriously old code".

Index: frame-unwind.c
===================================================================
RCS file: /cvs/src/src/gdb/frame-unwind.c,v
retrieving revision 1.7
diff -u -r1.7 frame-unwind.c
--- frame-unwind.c	4 Aug 2003 22:24:44 -0000	1.7
+++ frame-unwind.c	22 Feb 2004 17:08:07 -0000
@@ -74,7 +74,7 @@
   int i;
   struct gdbarch *gdbarch = get_frame_arch (next_frame);
   struct frame_unwind_table *table = gdbarch_data (gdbarch, frame_unwind_data);
-  if (!DEPRECATED_USE_GENERIC_DUMMY_FRAMES)
+  if (!DEPRECATED_USE_GENERIC_DUMMY_FRAMES && legacy_frame_p (gdbarch))
     /* Seriously old code.  Don't even try to use this new mechanism.
        (Note: The variable USE_GENERIC_DUMMY_FRAMES is deprecated, not
        the dummy frame mechanism.  All architectures should be using

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]