aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorJim Kingdon <jkingdon@engr.sgi.com>1994-01-13 00:34:18 +0000
committerJim Kingdon <jkingdon@engr.sgi.com>1994-01-13 00:34:18 +0000
commit470dfa0ca0be22f29333a8fdcb7733c94bb1b261 (patch)
tree24c02349974b84c2c2952919f7dc12e02372cfef /gdb
parent96f147a09543c98a60cc71c24cfb4834aac73bcd (diff)
downloadgdb-470dfa0ca0be22f29333a8fdcb7733c94bb1b261.zip
gdb-470dfa0ca0be22f29333a8fdcb7733c94bb1b261.tar.gz
gdb-470dfa0ca0be22f29333a8fdcb7733c94bb1b261.tar.bz2
* 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.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/ChangeLog6
-rw-r--r--gdb/objfiles.h5
2 files changed, 8 insertions, 3 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 36ea1a3..fea2cbe 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 bf1a930..6cff2ca 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