Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: eliz@gnu.org, dewar@adacore.com, nickrob@snap.net.nz,
		jan.kratochvil@redhat.com, Mathieu.Lacage@sophia.inria.fr,
		gdb@sourceware.org
Subject: Re: [RFC] Signed/unsigned character arrays are not strings
Date: Wed, 28 Feb 2007 14:35:00 -0000	[thread overview]
Message-ID: <20070228134640.GA11261@caradoc.them.org> (raw)
In-Reply-To: <200702272211.l1RMBVvI028239@brahms.sibelius.xs4all.nl>

On Tue, Feb 27, 2007 at 11:11:32PM +0100, Mark Kettenis wrote:
> Anyway, I'm in favour of restore the traditional gdb behaviour of
> printing all three as strings.

While I haven't seen responses to some of my arguments in favor of the
new behavior, it's obvious that I'm in the minority here.  So, the
behavior ought to change.

I was concerned about Jim's patch, but thinking about it some more, I
would be happy with it (probably with Paul's suggestion).  That's
because "typedef char *name" is reasonably common, but "typedef char
name_unit;" is much less so.  What do those who prefer the old
behavior think of that?

If it's no better, then we're back to what Jan suggested: something
which only works for the GDB int8_t and uint8_t types, to fix the
display of vector registers.

By the way, I was thinking about this last night and wondered if
this is hinting at a sensible meaning for "print /s" ...

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2007-02-28 13:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-24 16:13 Nick Roberts
2007-02-24 20:11 ` Daniel Jacobowitz
2007-02-24 20:53   ` Nick Roberts
2007-02-24 21:07     ` Jan Kratochvil
2007-02-25  8:00       ` Daniel Jacobowitz
2007-02-25 19:54         ` Nick Roberts
2007-02-25 21:07     ` mathieu lacage
2007-02-26  0:45       ` Jan Kratochvil
2007-02-27  7:17         ` Eli Zaretskii
2007-02-27  9:29         ` Daniel Jacobowitz
2007-02-27 12:02           ` Nick Roberts
2007-02-27 17:06             ` Robert Dewar
2007-02-27 18:42               ` Daniel Jacobowitz
2007-02-27 21:53                 ` Eli Zaretskii
2007-02-27 22:12                   ` Daniel Jacobowitz
2007-02-27 22:14                     ` Mark Kettenis
2007-02-28  0:47                       ` Paul Koning
2007-02-28  1:14                       ` Jim Blandy
2007-02-28  1:59                         ` Jim Blandy
2007-02-28  5:26                           ` Nick Roberts
2007-02-28 14:35                       ` Daniel Jacobowitz [this message]
2007-03-01  0:43                         ` Jim Blandy
2007-03-01  0:54                         ` Nick Roberts
2007-02-27 21:47               ` Eli Zaretskii
2007-02-27 22:12             ` Daniel Jacobowitz
2007-04-10 21:59         ` Daniel Jacobowitz
2007-02-28 13:05 pkoning
2007-03-01 11:01 ` Mark Kettenis

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=20070228134640.GA11261@caradoc.them.org \
    --to=drow@false.org \
    --cc=Mathieu.Lacage@sophia.inria.fr \
    --cc=dewar@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=nickrob@snap.net.nz \
    /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