public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "f.heckenbach@fh-soft.de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/16933] New: p omits trailing 0 when printing a range of chars Date: Mon, 12 May 2014 08:00:00 -0000 [thread overview] Message-ID: <bug-16933-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16933 Bug ID: 16933 Summary: p omits trailing 0 when printing a range of chars Product: gdb Version: 7.7 Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: f.heckenbach@fh-soft.de This bug was reported as Debian bug #666216 for gdb 7-0. According to Hector Oron, it is still reproducable with 7.7-1. p omits trailing 0 when printing a range of chars. To reproduce: # echo 'char foo[5] = { 1, 2, 0, 4, 0 };' > foo.c # gcc -c -g foo.c # gdb foo.o (gdb) p foo[0]@5 $1 = "\001\002\000\004" What I really wanted would be "{1, 2, 0, 4, 0}", like for other integer types, since I explicitly selected a single element and gave a range (@5), but if it must print it as a string, it should at least print all of the bytes. I know that's probably due to C's notorious confusion between integers and characters, and I also know there are other ways to dump some bytes in gdb. But still it seems plain wrong to print 4 chars if 5 items were explicitly requested, just because the last one happens to be 0. Note that it's not printing a 0-terminated string either: The embedded "\000" is printed; just one terminating 0 is omitted. (Which gets very confusing with larger arrays, if you look for something near the end, thinking the last one printed is the last one requested and then go hunting your off-by-one bug, only to realize later there wasn't any ...) -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-05-12 8:00 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-12 8:00 f.heckenbach@fh-soft.de [this message] 2014-05-12 16:29 ` [Bug gdb/16933] " schwab@linux-m68k.org 2014-05-12 16:38 ` f.heckenbach@fh-soft.de 2024-01-01 23:43 ` ssbssa at sourceware dot org 2024-01-10 16:26 ` ssbssa at sourceware dot org 2024-01-10 16:28 ` ssbssa at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-16933-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).