From: Tom Tromey <tromey@redhat.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Alexandre Oliva <aoliva@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFC][Python] Re: any expression to tell whether a variable was optimized out?
Date: Mon, 23 Mar 2009 17:47:00 -0000 [thread overview]
Message-ID: <m3bprs9lqg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1237771863.25721.17.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Sun\, 22 Mar 2009 22\:31\:02 -0300")
>>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
Tom> I'm a little surprised that this is an attribute of values at all.
Tom> Doesn't that seem weird? Is there anything useful that can be done
Tom> with a value like this? Perhaps just fetching its type?
Thiago> I guess Alexandre just found a use for the attribute. :-)
:)
Funnily enough, a couple of PRs related to this came in over the
weekend. And, those make it clear that we actually do want this as an
attribute of the value -- a future GCC may generate a value where some
components are defined and some are not. In this case we would want
to track the undefined bits and let value operations apply to defined
ones but not undefined ones. I think.
Thiago> This patch implements the attribute in gdb.Value, what do you think?
The code bits are ok.
Thiago> By the way, when writing this patch I realised that probably the
Thiago> "address" method in Value would better be turned into an attribute.
Do it :)
Thiago> Also, in the python branch, the "type" method also could be converted to
Thiago> an attribute.
The type method is still funny because, due to memory management
oddities, we always allocate a fresh Type. This has already bit a
user, though, and we ought to figure out how to fix it.
Tom
next prev parent reply other threads:[~2009-03-23 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <orskllhfo3.fsf@oliva.athome.lsd.ic.unicamp.br>
[not found] ` <20090310125945.GA4376@caradoc.them.org>
[not found] ` <1236700079.11106.1.camel@localhost.localdomain>
[not found] ` <orzlftfhu1.fsf@oliva.athome.lsd.ic.unicamp.br>
[not found] ` <1236710732.11106.30.camel@localhost.localdomain>
[not found] ` <m3hc1rluz1.fsf@fleche.redhat.com>
2009-03-23 2:09 ` Thiago Jung Bauermann
2009-03-23 4:24 ` Eli Zaretskii
2009-03-26 21:21 ` Thiago Jung Bauermann
2009-03-23 17:47 ` Tom Tromey [this message]
2009-03-28 21:38 ` [RFA][Python] Change gdb.Value.address from a method to an attribute Thiago Jung Bauermann
2009-03-29 4:21 ` Eli Zaretskii
2009-03-29 18:12 ` Tom Tromey
2009-03-29 18:56 ` Eli Zaretskii
2009-03-29 21:22 ` Thiago Jung Bauermann
2009-03-29 15:42 ` 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=m3bprs9lqg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=aoliva@redhat.com \
--cc=bauerman@br.ibm.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