This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[PATCH] Fix VAX frame IDs
- From: Mark Kettenis <kettenis at chello dot nl>
- To: gdb-patches at sources dot redhat dot com
- Date: Sun, 8 Aug 2004 12:40:27 +0200 (CEST)
- Subject: [PATCH] Fix VAX frame IDs
VAX was stepping into function calls for `next'. Turned out I used
the frame's current PC instead of the function's PC in constructing
the frame ID. Fixed by the attached patch. I'll also check this in
on the branch.
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* vax-tdep.c (vax_frame_this_id): Use frame_func_unwind instead of
frame_pc_unwind.
Index: vax-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/vax-tdep.c,v
retrieving revision 1.84
diff -u -p -r1.84 vax-tdep.c
--- vax-tdep.c 31 Jul 2004 21:53:17 -0000 1.84
+++ vax-tdep.c 8 Aug 2004 10:32:31 -0000
@@ -383,7 +383,7 @@ vax_frame_this_id (struct frame_info *ne
if (cache->base == 0)
return;
- (*this_id) = frame_id_build (cache->base, frame_pc_unwind (next_frame));
+ (*this_id) = frame_id_build (cache->base, frame_func_unwind (next_frame));
}
static void