[RFA,4/5] Document language choice in 'info [functions|variables|types]|rbreak' commands
Commit Message
doc/ChangeLog
2018-10-27 Philippe Waroquiers <philippe.waroquiers@skynet.be>
* gdb.texinfo (Examining the Symbol Table): Document language choice
for 'info types|functions|variables' commands.
(Setting Breakpoints): Document language choice to print
the functions in which a breakpoint is set.
---
gdb/doc/gdb.texinfo | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
Comments
> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Date: Sun, 28 Oct 2018 15:46:13 +0100
>
> +In programs using different languages, @value{GDBN} chooses the syntax
> +to print the list of all breakpoints it sets according to the
> +@samp{set language} value: using @samp{set language auto} means
> +to use the language of the breakpoint's function, other values mean to use
> +the manually specified language.
Please add a cross-reference to where "set language" is described,
here and in the other places where you make these changes.
Thanks.
@@ -3873,6 +3873,12 @@ breakpoints are set, they are treated just like the breakpoints set with
the @code{break} command. You can delete them, disable them, or make
them conditional the same way as any other breakpoint.
+In programs using different languages, @value{GDBN} chooses the syntax
+to print the list of all breakpoints it sets according to the
+@samp{set language} value: using @samp{set language auto} means
+to use the language of the breakpoint's function, other values mean to use
+the manually specified language.
+
The syntax of the regular expression is the standard one used with tools
like @file{grep}. Note that this is different from the syntax used by
shells, so for instance @code{foo*} matches all functions that include
@@ -17902,6 +17908,12 @@ types in your program whose names include the string @code{value}, but
@samp{i type ^value$} gives information only on types whose complete
name is @code{value}.
+In programs using different languages, @value{GDBN} chooses the syntax
+to print the type description according to the
+@samp{set language} value: using @samp{set language auto} means
+to use the language of the type, other values mean to use
+the manually specified language.
+
This command differs from @code{ptype} in two ways: first, like
@code{whatis}, it does not print a detailed description; second, it
lists all source files and line numbers where a type is defined.
@@ -17986,6 +17998,12 @@ Similarly to @samp{info types}, this command groups its output by source
files and annotates each function definition with its source line
number.
+In programs using different languages, @value{GDBN} chooses the syntax
+to print the function name and type according to the
+@samp{set language} value: using @samp{set language auto} means
+to use the language of the function, other values mean to use
+the manually specified language.
+
The optional flag @samp{-q}, which stands for @samp{quiet}, disables
printing header information and messages explaining why no functions
have been printed.
@@ -18026,6 +18044,12 @@ outside of functions (i.e.@: excluding local variables).
The printed variables are grouped by source files and annotated with
their respective source line numbers.
+In programs using different languages, @value{GDBN} chooses the syntax
+to print the variable name and type according to the
+@samp{set language} value: using @samp{set language auto} means
+to use the language of the variable, other values mean to use
+the manually specified language.
+
The optional flag @samp{-q}, which stands for @samp{quiet}, disables
printing header information and messages explaining why no variables
have been printed.