diff options
author | Andrew Cagney <cagney@redhat.com> | 2002-09-17 21:18:54 +0000 |
---|---|---|
committer | Andrew Cagney <cagney@redhat.com> | 2002-09-17 21:18:54 +0000 |
commit | 47a06d0591e9ef4ee9b4928f2bca70b488094865 (patch) | |
tree | 42f491c78e94bbba5d34d3b6d97bce4458a4eeb5 /gdb/arch-utils.c | |
parent | c00255e99c8b12f4f1c5d0c066afbb2add976fb9 (diff) | |
download | gdb-47a06d0591e9ef4ee9b4928f2bca70b488094865.tar.gz |
2002-09-17 Andrew Cagney <ac131313@redhat.com>
* arch-utils.c (legacy_virtual_frame_pointer): If FP_REGNUM is
invalid, return SP_REGNUM.
Diffstat (limited to 'gdb/arch-utils.c')
-rw-r--r-- | gdb/arch-utils.c | 15 |
1 files changed, 13 insertions, 2 deletions
diff --git a/gdb/arch-utils.c b/gdb/arch-utils.c index 3666bd55c06..a056177553e 100644 --- a/gdb/arch-utils.c +++ b/gdb/arch-utils.c @@ -423,8 +423,19 @@ legacy_virtual_frame_pointer (CORE_ADDR pc, int *frame_regnum, LONGEST *frame_offset) { - gdb_assert (FP_REGNUM >= 0); - *frame_regnum = FP_REGNUM; + /* FIXME: cagney/2002-09-13: This code is used when identifying the + frame pointer of the current PC. It is assuming that a single + register and an offset can determine this. I think it should + instead generate a byte code expression as that would work better + with things like Dwarf2's CFI. */ + if (FP_REGNUM >= 0 && FP_REGNUM < NUM_REGS) + *frame_regnum = FP_REGNUM; + else if (SP_REGNUM >= 0 && SP_REGNUM < NUM_REGS) + *frame_regnum = SP_REGNUM; + else + /* Should this be an internal error? I guess so, it is reflecting + an architectural limitation in the current design. */ + internal_error (__FILE__, __LINE__, "No virtual frame pointer available"); *frame_offset = 0; } |