Path: utzoo!utgpu!watmath!uunet!tut.cis.ohio-state.edu!rutgers!labrea!decwrl!alverson From: alverson@decwrl.dec.com (Robert Alverson) Newsgroups: gnu.gdb.bug Subject: Re: stack frame problem in 2.8.0? Message-ID: <983@bacchus.dec.com> Date: 13 Dec 88 02:19:47 GMT References: <3943@omepd> Organization: DEC Western Research Lab Lines: 33 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