From 64bb6c342081d0038c60180f298afac55640afaa Mon Sep 17 00:00:00 2001 From: Bruce Evans Date: Sun, 13 Jul 1997 14:31:54 +0000 Subject: Don't define HOST_DATA_START_ADDR, since gdb works without it the previous definition doesn't work on BSD4.4Lite[2] derived systems without the changes in rev.1.27 of kern_proc.c. --- gnu/usr.bin/gdb/bfd/i386freebsd.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'gnu') diff --git a/gnu/usr.bin/gdb/bfd/i386freebsd.h b/gnu/usr.bin/gdb/bfd/i386freebsd.h index af011311d795..4859a3797def 100644 --- a/gnu/usr.bin/gdb/bfd/i386freebsd.h +++ b/gnu/usr.bin/gdb/bfd/i386freebsd.h @@ -15,8 +15,9 @@ /* This seems to be the right thing for FreeBSD and BSDI */ #define HOST_STACK_END_ADDR USRSTACK -/* BSDI defines this too (PST) */ -#define HOST_DATA_START_ADDR ((bfd_vma)u.u_kproc.kp_eproc.e_vm.vm_daddr) +/* Leave HOST_DATA_START_ADDR undefined, since the default when it is not + defined sort of works, and FreeBSD-2.0 through FreeBSD-2.2.2 do not + set u.u_kproc.kp_eproc.e_vm.vm_daddr. */ #define TRAD_UNIX_CORE_FILE_FAILING_SIGNAL(core_bfd) \ ((core_bfd)->tdata.trad_core_data->u.u_sig) -- cgit v1.3