From: Roland Pesch Date: Wed, 21 Apr 1993 00:29:58 +0000 (+0000) Subject: (1) reduce the amount of text highlighted in warning at end of X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=b0157555b61c0c10416627739f185bc843b6adb1;p=binutils-gdb.git (1) reduce the amount of text highlighted in warning at end of "Program variables" section (2) introduce a few blank lines in menus to work around remaining makeinfo bugs --- diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 47d8cfca87e..e1b33b61957 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -164,6 +164,7 @@ This is Edition 4.07, January 1993, for GDB Version @value{GDBVN}. @ifclear BARETARGET * Sample Session:: A sample @value{GDBN} session @end ifclear + * Invocation:: Getting in and out of @value{GDBN} * Commands:: @value{GDBN} commands * Running:: Running programs under @value{GDBN} @@ -188,6 +189,7 @@ This is Edition 4.07, January 1993, for GDB Version @value{GDBVN}. @ifclear DOSHOST * Emacs:: Using @value{GDBN} under GNU Emacs @end ifclear + * GDB Bugs:: Reporting bugs in @value{GDBN} @ifset NOVEL * Renamed Commands:: @@ -199,6 +201,7 @@ This is Edition 4.07, January 1993, for GDB Version @value{GDBVN}. @ifclear AGGLOMERATION * Copying:: GNU GENERAL PUBLIC LICENSE @end ifclear + * Index:: Index @end menu @end ifinfo @@ -1914,6 +1917,7 @@ no effect on your program until you enable it again. @ifclear CONLY * Exception Handling:: Breakpoints and exceptions @end ifclear + * Delete Breaks:: Deleting breakpoints * Disabling:: Disabling breakpoints * Conditions:: Break conditions @@ -3199,6 +3203,7 @@ Emacs}. @ifclear DOSHOST * Search:: Searching source files @end ifclear + * Source Path:: Specifying source directories * Machine Code:: Source and machine code @end menu @@ -3697,17 +3702,17 @@ scope resolution operator in @value{GDBN} expressions. @cindex variable values, wrong @quotation @emph{Warning:} Occasionally, a local variable may appear to have the -wrong value at certain points in a function---just after entry to the -function, and just before exit. You may see this problem when you are -stepping by machine instructions. This is because on most machines, it -takes more than one instruction to set up a stack frame (including local -variable definitions); if you are stepping by machine instructions, -variables may appear to have the wrong values until the stack frame is -completely built. On function exit, it usually also takes more than one -machine instruction to destroy a stack frame; after you begin stepping -through that group of instructions, local variable definitions may be -gone. +wrong value at certain points in a function---just after entry to a new +scope, and just before exit. @end quotation +You may see this problem when you are stepping by machine instructions. +This is because on most machines, it takes more than one instruction to +set up a stack frame (including local variable definitions); if you are +stepping by machine instructions, variables may appear to have the wrong +values until the stack frame is completely built. On exit, it usually +also takes more than one machine instruction to destroy a stack frame; +after you begin stepping through that group of instructions, local +variable definitions may be gone. @node Arrays @section Artificial arrays @@ -6044,6 +6049,7 @@ its caller. @ifclear BARETARGET * Signaling:: Giving your program a signal @end ifclear + * Returning:: Returning from a function * Calling:: Calling your program's functions * Patching:: Patching your program