OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* gdb.texinfo (Ada Mode Intro): Improve the documentation regarding 

the direct visibility of all names in user-written packages.
This commit is contained in:
Joel Brobecker 2008-08-14 02:34:08 +00:00
parent 3d488bfcde
commit f3a2dd1a1d
2 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2008-08-13 Joel Brobecker <brobecker@adacore.com>
* gdb.texinfo (Ada Mode Intro): Improve the documentation regarding
the direct visibility of all names in user-written packages.
2008-08-13 Pedro Alves <pedro@codesourcery.com>
* gdb.texinfo (breakpoint always-inserted) Describe the auto mode

10
gdb/doc/gdb.texinfo
View File

@ -11071,11 +11071,11 @@ are not particularly important to the @value{GDBN} user.
That brevity is important to the @value{GDBN} user.
@end itemize
Thus, for brevity, the debugger acts as if there were
implicit @code{with} and @code{use} clauses in effect for all user-written
packages, making it unnecessary to fully qualify most names with
their packages, regardless of context. Where this causes ambiguity,
@value{GDBN} asks the user's intent.
Thus, for brevity, the debugger acts as if all names declared in
user-written packages are directly visible, even if they are not visible
according to Ada rules, thus making it unnecessary to fully qualify most
names with their packages, regardless of context. Where this causes
ambiguity, @value{GDBN} asks the user's intent.
The debugger will start in Ada mode if it detects an Ada main program.
As for other languages, it will enter Ada mode when stopped in a program that