[RFA/alpha-osf] another next frame confusion in signal unwinder?
Joel Brobecker
brobecker@adacore.com
Mon Dec 13 08:43:00 GMT 2004
> (I need to deprecate get frame base). Can you just tweak this to return
> get_frame_id().stack_addr before committing.
Sure. Attached is what I ended up checking in.
2004-12-13 Joel Brobecker <brobecker@gnat.com>
* alpha-osf1-tdep.c (alpha_osf1_sigcontext_addr): Change
parameter name to make it clear that we already have a next
frame. Return the sigcontext from that next frame instead
of the frame following it.
Thanks,
--
Joel
-------------- next part --------------
Index: alpha-osf1-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/alpha-osf1-tdep.c,v
retrieving revision 1.18
diff -u -p -r1.18 alpha-osf1-tdep.c
--- alpha-osf1-tdep.c 1 May 2004 15:34:49 -0000 1.18
+++ alpha-osf1-tdep.c 13 Dec 2004 05:04:53 -0000
@@ -35,14 +35,11 @@ alpha_osf1_pc_in_sigtramp (CORE_ADDR pc,
}
static CORE_ADDR
-alpha_osf1_sigcontext_addr (struct frame_info *frame)
+alpha_osf1_sigcontext_addr (struct frame_info *next_frame)
{
- struct frame_info *next_frame = get_next_frame (frame);
+ const struct frame_id next_id = get_frame_id (next_frame);
- if (next_frame != NULL)
- return (read_memory_integer (get_frame_base (next_frame), 8));
- else
- return (read_memory_integer (get_frame_base (frame), 8));
+ return (read_memory_integer (next_id.stack_addr, 8));
}
static void
More information about the Gdb-patches
mailing list