mirror/binutils-gdb
2
0
Fork 0
mirror of https://sourceware.org/git/binutils-gdb.git synced 2024-11-27 03:51:15 +08:00
Code Issues Packages Projects Releases Wiki Activity

* gdb.texinfo: Describe CHAR array vs. string identifcation rules.

Browse Source
This commit is contained in:
Jan Kratochvil 2007-01-26 20:53:52 +00:00
parent e784b426e6
commit 3a60f64edd
2 changed files with 25 additions and 0 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 @@
2007-01-26 Jan Kratochvil <jan.kratochvil@redhat.com>
Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo: Describe CHAR array vs. string identifcation rules.
2007-01-26 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (Compilation, Files, Bootstrapping, Bug Reporting):

20
gdb/doc/gdb.texinfo
View File

@ -5632,6 +5632,26 @@ If you ask to print an object whose contents are unknown to
by the debug information, @value{GDBN} will say @samp{<incomplete
type>}. @xref{Symbols, incomplete type}, for more about this.
Strings are identified as arrays of @code{char} values without specified
signedness. Arrays of either @code{signed char} or @code{unsigned char} get
printed as arrays of 1 byte sized integers. @code{-fsigned-char} or
@code{-funsigned-char} @value{NGCC} options have no effect as @value{GDBN}
defines literal string type @code{"char"} as @code{char} without a sign.
For program code
@smallexample
char var0[] = "A";
signed char var1[] = "A";
@end smallexample
You get during debugging
@smallexample
(gdb) print var0
$1 = "A"
(gdb) print var1
$2 = @{65 'A', 0 '\0'@}
@end smallexample
@node Arrays
@section Artificial arrays