diff options
| author | Tom Tromey <tromey@adacore.com> | 2023-05-31 08:28:01 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2023-05-31 08:28:01 -0600 |
| commit | 20fcd1747993127c648b9a3ad393a6caa3a025ba (patch) | |
| tree | 87ddc8af5668e950653bf3cd0e08bc7f769ad79e | |
| parent | 0b1cae3530601b0e5e16bb10cebafa69c43a3d09 (diff) | |
| download | binutils-20fcd1747993127c648b9a3ad393a6caa3a025ba.zip binutils-20fcd1747993127c648b9a3ad393a6caa3a025ba.tar.gz binutils-20fcd1747993127c648b9a3ad393a6caa3a025ba.tar.bz2 | |
Pass correct name to @value in gdb.texinfo
I noticed a couple instance of this warning when rebuilding the gdb
info files:
warning: undefined flag: GDB
The problem is that the wrong argument was passed to @value. This
patch fixes the problem.
| -rw-r--r-- | gdb/doc/gdb.texinfo | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 4bc83ed..a179af7 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -5972,8 +5972,8 @@ Handle the output by calling a function in your program (normally @code{printf}). When using this style the supported format specifiers depend entirely on the function being called. -Most of @value{GDB}'s format specifiers align with those supported by -the @code{printf} function, however, @value{GDB}'s @samp{%V} format +Most of @value{GDBN}'s format specifiers align with those supported by +the @code{printf} function, however, @value{GDBN}'s @samp{%V} format specifier extension is not supported by @code{printf}. When using @samp{call} style dprintf, care should be taken to ensure that only format specifiers supported by the output function are used, otherwise |