freebsd-dev/gnu/usr.bin/binutils/gdb
Bruce Evans 941b2747b6 Don't override FRAME_CHAIN(). If the current frame is valid, then
the previous frame is in the usual place even for traps, interrupts
and syscalls in the kernel, because the assembly language stubs
don't change the frame pointer.  The previous frame is just not for
the calling function.  We may as well depend on this as on magic to
determine the trap frame address.  The magic is in FRAME_SAVED_PC()
which elides the correct number of stubs (1) to go back to a pc that
matches the previous frame.

Removing fbsd_kern_frame_chain() fixes bugs in it.  Xsyscall was
misspelled as _Xsyscall (gdb removes one leading underscore), so
the tf_syscall frame type was never found.  This was harmless
because tf_normal works in all cases in fbsd_kern_frame_chain()
and Xsyscall is spelled correctly in fbsd_kern_frame_saved_pc()
where it matters.  There were style bugs on almost every line,
starting with a primary indent of 7.
1998-01-18 12:35:48 +00:00
..
i386 Don't override FRAME_CHAIN(). If the current frame is valid, then 1998-01-18 12:35:48 +00:00
config.h changes required in the gdb directory for making gdb 1997-01-15 22:37:09 +00:00
gdb.1 change kvm-fbsd.c so that kernel debugging works again. 1997-04-27 21:36:49 +00:00
kvm-fbsd.c Don't override FRAME_CHAIN(). If the current frame is valid, then 1998-01-18 12:35:48 +00:00
Makefile Changes to support full make parallelism (-j<n>) in the world 1997-10-05 09:40:24 +00:00