From 470dfa0ca0be22f29333a8fdcb7733c94bb1b261 Mon Sep 17 00:00:00 2001 From: Jim Kingdon Date: Thu, 13 Jan 1994 00:34:18 +0000 Subject: [PATCH] * objfiles.h: Fix comments to reflect the fact that the phrase "top of stack" always refers to where the pushing and popping takes place, regardless of whether it is at the highest or lowest address. --- gdb/ChangeLog | 6 ++++++ gdb/objfiles.h | 5 ++--- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 36ea1a3e8f3..fea2cbe72cc 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,9 @@ +Wed Jan 12 19:32:11 1994 Jim Kingdon (kingdon@lioth.cygnus.com) + + * objfiles.h: Fix comments to reflect the fact that the phrase + "top of stack" always refers to where the pushing and popping takes + place, regardless of whether it is at the highest or lowest address. + Wed Jan 12 13:23:37 1994 Peter Schauer (pes@regent.e-technik.tu-muenchen.de) * mdebugread.c (parse_symbol): Do not set TYPE_TAG_NAME for diff --git a/gdb/objfiles.h b/gdb/objfiles.h index bf1a930ffdc..6cff2cad93e 100644 --- a/gdb/objfiles.h +++ b/gdb/objfiles.h @@ -40,10 +40,9 @@ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. */ executable which correspond to the "startup file", I.E. crt0.o in most cases. This file is assumed to be a startup file and frames with pc's inside it are treated as nonexistent. Setting these variables is necessary - so that backtraces do not fly off the bottom of the stack (or top, depending - upon your stack orientation). + so that backtraces do not fly off the bottom of the stack. - Gdb also supports an alternate method to avoid running off the top/bottom + Gdb also supports an alternate method to avoid running off the bottom of the stack. There are two frames that are "special", the frame for the function -- 2.30.2