From: Klee Dienes <klee@apple.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Print vector registers in natural format, not hex
Date: Mon, 04 Nov 2002 20:02:00 -0000 [thread overview]
Message-ID: <5769348C-F073-11D6-8361-00039396EEB8@apple.com> (raw)
In-Reply-To: <15792.38707.400671.968851@localhost.redhat.com>
I think it's definitely a misfeature. It's would be different if GDB
were skipping all the trailing nulls, and not just the final null ...
but either way, I think it's the wrong behavior. An array is an array,
not a string, and printing:
$1 = "abcd\000\000\000\000\000"
instead of
$1 = "abcd\000\000\000\000\000\000"
for 'char buf[10] = "hello"'
just seems much more confusing than useful.
On Friday, October 18, 2002, at 07:20 PM, Elena Zannoni wrote:
>
> And you haven't noticed this comment in the testfile, I take it :-) I
> discovered this while writing the vector support, but didn't fix it. I
> don't know that it actually needs to be fixed. It's a feature, not a
> bug, one could argue.
>
> # Note: in LE case, the char array is printed WITHOUT the last
> character.
> # Gdb treats the terminating null char in the array like the
> terminating
> # null char in a string and doesn't print it. This is not a failure,
> but
> # the way gdb works.
>
> Elena
next prev parent reply other threads:[~2002-11-05 4:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 13:41 Klee Dienes
2002-10-04 13:52 ` Daniel Jacobowitz
2002-10-04 14:11 ` Klee Dienes
2002-10-04 14:36 ` Daniel Jacobowitz
2002-10-18 16:23 ` Elena Zannoni
2002-11-04 20:02 ` Klee Dienes [this message]
2002-11-04 20:34 ` Daniel Jacobowitz
2002-10-05 10:29 ` Eli Zaretskii
2002-10-05 13:03 ` Klee Dienes
2002-10-06 11:31 ` Eli Zaretskii
2002-10-11 9:26 ` Klee Dienes
2002-10-12 2:01 ` Eli Zaretskii
2002-10-21 17:23 ` Andrew Cagney
2002-10-18 16:37 ` Elena Zannoni
2002-11-05 0:48 ` Klee Dienes
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=5769348C-F073-11D6-8361-00039396EEB8@apple.com \
--to=klee@apple.com \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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: link
Be 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