[RFC/RFA/frame stuff] Fix build failure in alpha-osf1-tdep.c

Joel Brobecker brobecker@gnat.com
Wed Jun 4 05:31:00 GMT 2003


> Yes.  If you're feeling game you could use get_frame_memory, but either way.

I will have a look at get_frame_memory, at least just out of curiosity.
But right now, here is the patch I ended up committing. Since
alpha_osf1_skip_sigtramp_frame is to be slain in a separate patch,
I didn't include the update in this patch.

2003-06-03  J. Brobecker  <brobecker@gnat.com>

        * alpha-osf1-tdep.c (alpha_osf1_sigcontext_addr): Replace
        references to struct frame_info fields by calls to the equivalent
        accessors. Necessary now that frame_info is opaque.

Thanks,
-- 
Joel
-------------- next part --------------
Index: alpha-osf1-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/alpha-osf1-tdep.c,v
retrieving revision 1.12
diff -c -3 -p -r1.12 alpha-osf1-tdep.c
*** alpha-osf1-tdep.c	3 Jun 2003 23:49:32 -0000	1.12
--- alpha-osf1-tdep.c	4 Jun 2003 05:06:58 -0000
*************** alpha_osf1_pc_in_sigtramp (CORE_ADDR pc,
*** 50,57 ****
  static CORE_ADDR
  alpha_osf1_sigcontext_addr (struct frame_info *frame)
  {
!   return (read_memory_integer (frame->next ? frame->next->frame
! 					   : frame->frame, 8));
  }
  
  /* This is the definition of CALL_DUMMY_ADDRESS.  It's a heuristic that is used
--- 37,48 ----
  static CORE_ADDR
  alpha_osf1_sigcontext_addr (struct frame_info *frame)
  {
!   struct frame_info *next_frame = get_next_frame (frame);
! 
!   if (next_frame != NULL)
!     return (read_memory_integer (get_frame_base (next_frame), 8));
!   else
!     return (read_memory_integer (get_frame_base (frame), 8));
  }
  
  /* This is the definition of CALL_DUMMY_ADDRESS.  It's a heuristic that is used


More information about the Gdb-patches mailing list