Restore our local changes which were clobbered by the previous commit.

cvs is not being used effectively for gdb.  Our old changes get clobbered
and our new changes are mixed with "vendor" changes in the same updates
so they will be difficult to untangle for the next release of gdb.  The
revision logs get spammed for each release of gdb.
This commit is contained in:
bde 1994-12-31 16:34:59 +00:00
parent 842e88b134
commit 58e70655dc

View File

@ -30,12 +30,13 @@
#ifdef __bsdi__ #ifdef __bsdi__
/* This seems to be the right thing for BSDI. */ /* This seems to be the right thing for BSDI. */
#define HOST_STACK_END_ADDR USRSTACK #define HOST_STACK_END_ADDR USRSTACK
#define HOST_DATA_START_ADDR ((bfd_vma)u.u_kproc.kp_eproc.e_vm.vm_daddr)
#else #else
/* This seems to be the right thing for 386BSD release 0.1. */ /* This seems to be the right thing for 386BSD release 0.1. */
#define HOST_STACK_END_ADDR (USRSTACK - MAXSSIZ) #define HOST_STACK_END_ADDR (USRSTACK - MAXSSIZ)
#endif #endif
#define HOST_DATA_START_ADDR ((bfd_vma)u.u_kproc.kp_eproc.e_vm.vm_daddr)
#define TRAD_UNIX_CORE_FILE_FAILING_SIGNAL(core_bfd) \ #define TRAD_UNIX_CORE_FILE_FAILING_SIGNAL(core_bfd) \
((core_bfd)->tdata.trad_core_data->u.u_sig) ((core_bfd)->tdata.trad_core_data->u.u_sig)
#define u_comm u_kproc.kp_proc.p_comm #define u_comm u_kproc.kp_proc.p_comm