Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA/commit/Ada] Wrong value printed by info locals for  dynamic object.
Date: Tue, 20 Apr 2010 23:03:00 -0000	[thread overview]
Message-ID: <20100420230318.GV19194@adacore.com> (raw)
In-Reply-To: <1271715891-8764-1-git-send-email-y>

>   return val_print (value_type (val), value_contents_all (val),
>                     value_embedded_offset (val), value_address (val),
>                     stream, recurse, options, language);
> 
> Short of creating a language-specific value_contents routine, I think
> that this was the best/easiest compromise... Thoughts on that?

Well, stupid me (again!): I just realized that I checked in a couple
of patches for which I said yesterday that I'd wait a few days. Sorry
about that.  Hopefully this is not a problem, but I'm happy to revert
and/or adjust based on feedback. My entire week is dedicated to the
FSF tree, so I have time...

-- 
Joel


  reply	other threads:[~2010-04-20 23:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 22:25 y
2010-04-20 23:03 ` Joel Brobecker [this message]
2010-04-21  1:07   ` 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=20100420230318.GV19194@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@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: 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