* config/alpha/tm-fbsd.h (FRAME_CHAIN_VALID): Remove.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 74d3ba926ac4fd7721c378a48ae97b5979b6b621..5698447858fcce4bf4d4761cfab2e0cf68c2732d 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2002-04-21  Jason Thorpe  <thorpej@wasabisystems.com>
+
+       * config/alpha/tm-fbsd.h (FRAME_CHAIN_VALID): Remove.
+
 2002-04-21  Andrew Cagney  <ac131313@redhat.com>
 
        * 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 55b3877018e29fcdbd40c2c2c1614b5770d7bebd..d1d525466ec7deb6d77d23ff8d1766085ea2115d 100644 (file)
--- 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.  */