From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: partially fix empty DW_OP_piece
Date: Fri, 14 May 2010 22:51:00 -0000 [thread overview]
Message-ID: <20100514223521.GA3975@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3vdars0hy.fsf@fleche.redhat.com>
On Fri, 14 May 2010 04:03:37 +0200, Tom Tromey wrote:
> The other way is to simply remove val_print entirely and make all of
> printing work using values. I think this is the route I would prefer.
That could hopefully solve the problem of missing type-associated object
address for DW_OP_push_object_address for the VLA (variable length arrays)
patch.
> @@ -366,6 +366,14 @@ read_pieced_value (struct value *v)
> + case DWARF_VALUE_OPTIMIZED_OUT:
> + /* We just leave the bits empty for now. This is not ideal
> + but gdb currently does not have a nice way to represent
> + optimized-out pieces. */
> + warning (_("some bits in computed object were optimized out; "
> + "replacing with zeroes"));
> + break;
If it would go in I would prefer to at least print the bit/byte range.
Thanks,
Jan
next prev parent reply other threads:[~2010-05-14 22:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 6:39 Tom Tromey
2010-05-14 22:51 ` Jan Kratochvil [this message]
2010-05-21 19:48 ` Tom Tromey
2010-06-01 17:34 ` Tom Tromey
2010-06-02 18:54 ` Jan Kratochvil
2010-06-02 20:07 ` Tom Tromey
2010-06-03 17:46 ` Jan Kratochvil
2010-06-04 19:05 ` Tom Tromey
2010-06-04 19:10 ` Jan Kratochvil
2010-06-04 21:39 ` Tom Tromey
2010-06-04 21:47 ` Jan Kratochvil
2010-05-20 23:04 ` Joel Brobecker
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=20100514223521.GA3975@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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