From d6434f3974a54ad6498c23327414c01ca3a5241c Mon Sep 17 00:00:00 2001 From: John Gilmore Date: Sat, 29 Aug 1992 04:22:31 +0000 Subject: Minor bug fixes from last big checkin. --- gdb/rs6000-tdep.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'gdb/rs6000-tdep.c') diff --git a/gdb/rs6000-tdep.c b/gdb/rs6000-tdep.c index 5bee145..45d6af4 100644 --- a/gdb/rs6000-tdep.c +++ b/gdb/rs6000-tdep.c @@ -39,12 +39,14 @@ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. */ #include #include + +extern struct obstack frame_cache_obstack; + extern int errno; /* Nonzero if we just simulated a single step break. */ int one_stepped; - /* Breakpoint shadows for the single step instructions will be kept here. */ static struct sstep_breaks { @@ -399,7 +401,7 @@ FIXME: This whole concept is broken. You should be able to detect a dummy stack frame *on the user's stack itself*. When you do, then you know the format of that stack frame -- including its saved SP register! There should *not* be a separate stack in the -GDB process that keeps track of these dummy frames! -- gnu@cygnus.com Aug92 */ +GDB process that keeps track of these dummy frames! -- gnu@cygnus.com Aug92 */ pop_dummy_frame () @@ -546,7 +548,7 @@ fix_call_dummy(dummyname, pc, fun, nargs, type) */ void function_frame_info (pc, fdata) - int pc; + CORE_ADDR pc; struct aix_framedata *fdata; { unsigned int tmp; -- cgit v1.1