From 9c1d6fe5536783eb7199ca7767f7ee74d5e9e6fd Mon Sep 17 00:00:00 2001 From: Jason Thorpe Date: Sun, 21 Apr 2002 20:17:28 +0000 Subject: [PATCH] * config/alpha/tm-fbsd.h (FRAME_CHAIN_VALID): Remove. --- gdb/ChangeLog | 4 ++++ gdb/config/alpha/tm-fbsd.h | 7 ------- 2 files changed, 4 insertions(+), 7 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 74d3ba926ac..5698447858f 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2002-04-21 Jason Thorpe + + * config/alpha/tm-fbsd.h (FRAME_CHAIN_VALID): Remove. + 2002-04-21 Andrew Cagney * arm-tdep.c (arm_breakpoint_from_pc): Make static. Make return diff --git a/gdb/config/alpha/tm-fbsd.h b/gdb/config/alpha/tm-fbsd.h index 55b3877018e..d1d525466ec 100644 --- a/gdb/config/alpha/tm-fbsd.h +++ b/gdb/config/alpha/tm-fbsd.h @@ -23,13 +23,6 @@ #include "alpha/tm-alpha.h" -/* FreeBSD doesn't mark the outermost frame. While some FreeBSD/Alpha - releases include (a minimal amount of) debugging info in its - startup code (crt1.o), the safest thing is to consider the user - code entry point as the outermost frame. */ -#define FRAME_CHAIN_VALID(chain, thisframe) \ - func_frame_chain_valid(chain, thisframe) - /* Number of traps that happen between exec'ing the shell to run an inferior, and when we finally get to the inferior code. The default is right for FreeBSD. */ -- 2.30.2