yggdrasil/binutils-gdb
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove "Ada Settings" node from the manual

Browse Source 
A while back, I sent a patch to unify the Ada varsize-limit setting
with the more generic max-value-size:

https://sourceware.org/pipermail/gdb-patches/2021-September/182004.html

However, it turns out I somehow neglected to send part of the patch.
Internally, I also removed the "Ada Settings" node from the manual, as
it only documents the obsolete setting.

This patch removes this text.
This commit is contained in:
Tom Tromey 2022-03-14 08:01:12 -06:00
parent 44a29af963
commit dc262faf37
1 changed files with 0 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
gdb/doc/gdb.texinfo
View File

@ -18137,7 +18137,6 @@ to be difficult.
* Ada Tasks and Core Files:: Tasking Support when Debugging Core Files
* Ravenscar Profile:: Tasking Support when using the Ravenscar
Profile
* Ada Settings:: New settable GDB parameters for Ada.
* Ada Source Character Set:: Character set of Ada source files.
* Ada Glitches:: Known peculiarities of Ada mode.
@end menu
@ -18871,37 +18870,6 @@ it isn't currently possible to single-step through the runtime
initialization sequence. If you need to debug this code, you should
use @code{set ravenscar task-switching off}.
@node Ada Settings
@subsubsection Ada Settings
@cindex Ada settings
@table @code
@kindex set varsize-limit
@item set varsize-limit @var{size}
Prevent @value{GDBN} from attempting to evaluate objects whose size
is above the given limit (@var{size}) when those sizes are computed
from run-time quantities. This is typically the case when the object
has a variable size, such as an array whose bounds are not known at
compile time for example. Setting @var{size} to @code{unlimited}
removes the size limitation. By default, the limit is about 65KB.
The purpose of having such a limit is to prevent @value{GDBN} from
trying to grab enormous chunks of virtual memory when asked to evaluate
a quantity whose bounds have been corrupted or have not yet been fully
initialized. The limit applies to the results of some subexpressions
as well as to complete expressions. For example, an expression denoting
a simple integer component, such as @code{x.y.z}, may fail if the size of
@code{x.y} is variable and exceeds @code{size}. On the other hand,
@value{GDBN} is sometimes clever; the expression @code{A(i)}, where
@code{A} is an array variable with non-constant size, will generally
succeed regardless of the bounds on @code{A}, as long as the component
size is less than @var{size}.
@kindex show varsize-limit
@item show varsize-limit
Show the limit on types whose size is determined by run-time quantities.
@end table
@node Ada Source Character Set
@subsubsection Ada Source Character Set
@cindex Ada, source character set