This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[PATCH] Fix FreeBSD/Alpha outermost frame detection mechanism
- To: gdb-patches at sources dot redhat dot com
- Subject: [PATCH] Fix FreeBSD/Alpha outermost frame detection mechanism
- From: Mark Kettenis <kettenis at wins dot uva dot nl>
- Date: Sat, 6 Oct 2001 21:21:21 +0200
Apparently FreeBSD-current on Alpha no longer contains the .mdebug
info that helped us to determine what's the outermost frame. Fixed by
#defining FRAME_CHAIN_VALID to use func_frame_chain_valid.
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@beast.freebsd.org>
* config/alpha/tm-fbsd.h (FRAME_CHAIN_VALID): Define.
Index: config/alpha/tm-fbsd.h
===================================================================
RCS file: /cvs/src/src/gdb/config/alpha/tm-fbsd.h,v
retrieving revision 1.2
diff -u -p -r1.2 tm-fbsd.h
--- config/alpha/tm-fbsd.h 2001/01/25 18:41:22 1.2
+++ config/alpha/tm-fbsd.h 2001/10/06 19:17:48
@@ -29,6 +29,13 @@
#define USE_STRUCT_CONVENTION(gcc_p, type) \
alphafbsd_use_struct_convention (gcc_p, type)
+/* 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. */