From: Pedro Alves <palves@redhat.com>
To: Martin Galvan <martin.galvan@tallertechnologies.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v3][PR gdb/19893] Fix handling of synthetic C++ references
Date: Tue, 31 May 2016 14:23:00 -0000 [thread overview]
Message-ID: <67dc8b18-2006-4309-4b18-4c8080e89250@redhat.com> (raw)
In-Reply-To: <f304ad49-fe80-c7f3-bf4c-71aed85e2429@redhat.com>
On 05/31/2016 03:13 PM, Pedro Alves wrote:
> Otherwise OK. Please push.
Actually, I take that back, sorry. I forgot something:
>> + Notice that for references to TYPE_CODE_STRUCT, 'set print object on' will
>> + cause original_value to be a not_lval instead of an lval_computed,
>> + which will make value_bits_synthetic_pointer return false.
I still think it'd be very good to have this covered
with a test.
I think it should be a matter of wrapping the printing
part of new tests (maybe only implref-struct.exp, not sure), with:
foreach_with_prefix print-object {"off" "off"} {
gdb_test_no_output "set print object ${print-object}"
... ref printing tests ...
}
Could you do that please?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-05-31 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 19:41 Martin Galvan
2016-05-31 14:13 ` Pedro Alves
2016-05-31 14:23 ` Pedro Alves [this message]
2016-05-31 14:25 ` Martin Galvan
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=67dc8b18-2006-4309-4b18-4c8080e89250@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=martin.galvan@tallertechnologies.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