public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Paul Koning <Paul_Koning@dell.com>
Cc: "Elmenthaler, Jens" <jens.elmenthaler@verigy.com>,
	gdb@sourceware.org, archer@sourceware.org, dje@google.com
Subject: Re: [python] Pretty-printers and addressprint
Date: Tue, 10 Nov 2009 15:45:00 -0000	[thread overview]
Message-ID: <8ac60eac0911100744t5335a44fn7175e2d5c512e450@mail.gmail.com> (raw)
In-Reply-To: <D8CEBB6AE9D43848BD2220619A43F3263EB947@M31.equallogic.com>

On Tue, Nov 10, 2009 at 3:53 AM, Paul Koning <Paul_Koning@dell.com> wrote:

>> Unfortunately I frequently deal with non-ascii strings, and the
>> problem just wouldn't go away :-(
>
> My test (without gdb, I don't have that installed yet) is inconclusive
> but I think using repr() will cure that too.

AFAICT, in GDB repr(value) is a no-op, and the end result of returning
repr(value) from the pretty-printer is exactly the same as that of
returning the value itself:

  $4 = 0x4007e0 "this is x\201\202\203\204"

Should repr(value) do something different?

Thanks,
-- 
Paul Pluzhnikov

  reply	other threads:[~2009-11-10 15:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10  2:12 Paul Pluzhnikov
2009-11-10  7:25 ` Elmenthaler, Jens
2009-11-10  8:06   ` Paul Pluzhnikov
2009-11-10  8:37     ` Phil Muldoon
2009-11-10 11:53     ` Paul Koning
2009-11-10 15:45       ` Paul Pluzhnikov [this message]
2009-11-10 15:53         ` Paul Koning
2009-11-10 16:53         ` Tom Tromey
2009-11-10 17:03           ` Paul Pluzhnikov
2009-11-10 20:49             ` Tom Tromey
2009-11-10 15:12 ` Tom Tromey

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=8ac60eac0911100744t5335a44fn7175e2d5c512e450@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=Paul_Koning@dell.com \
    --cc=archer@sourceware.org \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=jens.elmenthaler@verigy.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).