Thread View: gnu.gdb.bug
2 messages
2 total messages
Started by Chris Benenati
Wed, 23 Nov 1988 02:24
stack frame problem in 2.8.0?
Author: Chris Benenati
Date: Wed, 23 Nov 1988 02:24
Date: Wed, 23 Nov 1988 02:24
16 lines
762 bytes
762 bytes
I just built a VAX version of gdb+ V2.8.0 and am running under 4.3 BSD. No matter how many routines down I am, gdb only seems to know about the current stack frame: 'bt' displays only a level 0 frame, 'up' refuses to work, etc. Has anybody else run into this problem? Or did I just screw up when I built gdb? Thanks.
Re: stack frame problem in 2.8.0?
Author: Robert Alverson
Date: Tue, 13 Dec 1988 02:19
Date: Tue, 13 Dec 1988 02:19
33 lines
1562 bytes
1562 bytes
I've brought up gdb+ 2.8.0 on a vax running Ultrix 3.0.
This is a bug in m-vax.h, I think. Here are the diffs:
*** m-vax.h Mon Dec 12 17:54:59 1988
--- m-vax.h.BAK Mon Dec 12 17:24:15 1988
***************
*** 218,224
/* Define other aspects of the stack frame. */
! #define FRAME_SAVED_PC(frame, ignore) (read_memory_integer (frame + 16, 4), 0)
/* Cannot find the AP register value directly from the FP value.
Must find it saved in the frame called by this one, or in the AP register
--- 218,224 -----
/* Define other aspects of the stack frame. */
! #define FRAME_SAVED_PC(frame, ignore) (read_memory_integer (frame + 16, 4))
/* Cannot find the AP register value directly from the FP value.
Must find it saved in the frame called by this one, or in the AP register
In addition, when I compiled expread.y with yacc, I got 101 shift/reduce
conflicts, and 1 reduce/reduce conflict. I've modified the grammar
so that it compiles with only 1 shift/reduce conflict and 1 reduce/reduce
conflict. Those relate to C++ features that I haven't figured out yet.
I need to check my fixes though, so no posting yet.
Bob <alverson@decwrl.dec.com>
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads