public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: David Blaikie <dblaikie@gmail.com>
To: Luke Drummond <luke.drummond@codeplay.com>, Tom Tromey <tom@tromey.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Concatenating LazyStrings
Date: Fri, 5 Nov 2021 12:55:27 -0700	[thread overview]
Message-ID: <CAENS6Et2tNWUBo6MKwfL1uw4GU6SHrWhZgO8jv2nAD__Hoqmww@mail.gmail.com> (raw)
In-Reply-To: <CFHUCMOS7Q40.3EPMGJ75KGPMY@lukedrummondpc>

Oh, huh, just gdb::Value's "string()" worked for me in the end - I was
dealing with some other layers of indirection/existing oddities in my
pretty printer codebase that had complicated things.

Thanks for the nudges in the right direction!

On Fri, Nov 5, 2021 at 5:22 AM Luke Drummond <luke.drummond@codeplay.com>
wrote:

> Hi David
>
> On Fri Nov 5, 2021 at 3:14 AM GMT, David Blaikie via Gdb wrote:
> > If I've got a pretty printer (for instance, for llvm's Twine type (
> >
> https://github.com/llvm/llvm-project/blob/6d03227c16ee1950db0e1aa05fbc3201770248eb/llvm/utils/gdb-scripts/prettyprinters.py#L354
> > + https://llvm.org/doxygen/classllvm_1_1Twine.html ) that wants to
> > pretty
> > print a string made up of other strings (from other pretty printers) -
> > how
> > would I do that?
> >
> > Specifically, I can't figure out how to correctly concatenate a gdb
> > LazyString value with another string. (even if I have to stringify the
> > LazyString (making it unlazy) in the process - calling ".value()" on the
> > LazyString doesn't seem to be enough - I can't seem to figure out how to
> > to-string-ify that resulting gdb Value (it doesn't have a pretty printer
> > that I can find - nor a to_string/str/string() function) to then
> > concatenate it with another string)
>
>
> `LazyString.value().format_string()` might be what you want. I've also
> found the
> python builtin `str()` function to be usable in many places.


>
> https://sourceware.org/gdb/onlinedocs/gdb/Values-From-Inferior.html#Values-From-Inferior
>
> has the documentation if you haven't already seen it.
>
> As an example, here's how I format an enumeration that's made up of
> bit-flags:
>
>         def fmt_flags_enum(enum_type, val):
>                         val = int(val)
>                         return ' | '.join(
>                                         gdb.Value((1 << x) &
> val).cast(enum_type).format_string()
>                                         for x in range(val.bit_length())
>                                         if (1 << x) & val
>                         )
>
>
> The `format_string()` converts the individual enumerators into a string
> that
> python can concatenate with `str.join`.
>
> Hope that helps.
>
> All the Best
>
> Luke
>
>
> --
> Codeplay Software Ltd.
> Company registered in England and Wales, number: 04567874
> Registered office: Regent House, 316 Beulah Hill, London, SE19 3HF
>

      reply	other threads:[~2021-11-05 19:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05  3:14 David Blaikie
2021-11-05 12:22 ` Luke Drummond
2021-11-05 19:55   ` David Blaikie [this message]

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=CAENS6Et2tNWUBo6MKwfL1uw4GU6SHrWhZgO8jv2nAD__Hoqmww@mail.gmail.com \
    --to=dblaikie@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=luke.drummond@codeplay.com \
    --cc=tom@tromey.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).