FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* objfiles.h: Fix comments to reflect the fact that the phrase

Browse source 
"top of stack" always refers to where the pushing and popping takes
	place, regardless of whether it is at the highest or lowest address.
This commit is contained in:
Jim Kingdon 1994-01-13 00:34:18 +00:00
parent 96f147a095
commit 470dfa0ca0
2 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
gdb/ChangeLog
View file

@ -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

5
gdb/objfiles.h
View file

@ -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