From 5e5592e692fedaf8b1e6c5371e72007ee39cf93d Mon Sep 17 00:00:00 2001 From: Andrew Cagney Date: Sat, 5 Apr 2003 15:39:34 +0000 Subject: 2003-04-05 Andrew Cagney * frame.c (get_frame_id): Update comment. (legacy_get_prev_frame): Update comment. * gdbarch.sh: Delete check for EXTRA_FRAME_INFO. * gdbarch.h: Regenerate. * config/sparc/tm-sparc.h (EXTRA_FRAME_INFO): Delete. * frame.h: Delete #ifdef EXTRA_FRAME_INFO code. --- gdb/frame.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) (limited to 'gdb/frame.c') diff --git a/gdb/frame.c b/gdb/frame.c index 9249005..1c65339 100644 --- a/gdb/frame.c +++ b/gdb/frame.c @@ -65,9 +65,7 @@ get_frame_id (struct frame_info *fi) fi->unwind->this_id (fi->next, &fi->prologue_cache, &fi->id); fi->id_p = 1; /* FIXME: cagney/2002-12-18: Instead of this hack, should only - store the frame ID in PREV_FRAME. Unfortunatly, some - architectures (HP/UX) still reply on EXTRA_FRAME_INFO and, - hence, still poke at the "struct frame_info" object directly. */ + store the frame ID in PREV_FRAME. */ fi->frame = fi->id.base; } return frame_id_build (fi->frame, get_frame_pc (fi)); @@ -1150,9 +1148,7 @@ legacy_get_prev_frame (struct frame_info *this_frame) frame base, in the frame object. */ /* FIXME: cagney/2002-12-18: Instead of this hack, should only - store the frame ID in PREV_FRAME. Unfortunatly, some - architectures (HP/UX) still reply on EXTRA_FRAME_INFO and, - hence, still poke at the "struct frame_info" object directly. */ + store the frame ID in PREV_FRAME. */ /* FIXME: cagney/2003-04-04: Once ->frame is eliminated, this assignment can go. */ prev->frame = prev->id.base; -- cgit v1.1