Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Paul Koning <paulkoning@comcast.net>
Cc: gdb-patches@sourceware.org
Subject: Re: Python: fetch value when building gdb.Value object
Date: Thu, 20 Oct 2011 15:09:00 -0000	[thread overview]
Message-ID: <m3wrbzpuwi.fsf@fleche.redhat.com> (raw)
In-Reply-To: <92D17899-A614-4333-87BE-E9746DFB8AB8@comcast.net> (Paul Koning's	message of "Wed, 19 Oct 2011 16:56:07 -0400")

Tom> Yes, I think so.  I think the current approach is going to bite us
Tom> later.  We already have bugs open about bad memory management using
Tom> gdb.Value.

Paul> Ok, I will work on that.

Thanks.

Paul> Then the other part will be a documentation change, to spell out
Paul> clearly the fact that operating on a gdb.Value type can raise an
Paul> exception at that time.  For example, for a Value object v, the
Paul> expression "v+1" can result in an exception (unlike what is
Paul> usually true for Python variables of most types).

Yes, that sounds good.

Also, we can expose the laziness directly to Python.  I filed a PR for
this:

http://sourceware.org/bugzilla/show_bug.cgi?id=13327

Tom


  reply	other threads:[~2011-10-20 15:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 16:17 Paul Koning
2011-09-28 19:29 ` Phil Muldoon
2011-09-28 20:06   ` Paul Koning
2011-10-04 15:43     ` Tom Tromey
2011-09-28 20:42   ` Paul Koning
2011-10-01  9:05     ` Jan Kratochvil
2011-10-03 10:22       ` Phil Muldoon
2011-10-04 15:40       ` Tom Tromey
2011-10-01  9:29   ` Jan Kratochvil
2011-10-01 10:23     ` Pedro Alves
2011-10-01 11:03       ` Jan Kratochvil
2011-10-01 12:17     ` Python: fetch value when building gdb.Value object [rediff] Jan Kratochvil
2011-10-01 18:58       ` Paul Koning
2011-10-03 10:19       ` Phil Muldoon
2011-10-03 16:16         ` Paul Koning
2011-10-01  1:00 ` [PING] [RFA] Re: Python: fetch value when building gdb.Value object Paul Koning
2011-10-04 15:45 ` Tom Tromey
2011-10-04 15:51   ` Paul Koning
2011-10-14 20:03     ` Tom Tromey
2011-10-14 20:30       ` Paul Koning
2011-10-19 20:56         ` Tom Tromey
2011-10-19 20:58           ` Paul Koning
2011-10-20 15:09             ` Tom Tromey [this message]
2011-10-21  7:46               ` Paul Koning
2011-10-21 17:13                 ` Tom Tromey
2011-10-14 23:36   ` Jim Blandy

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=m3wrbzpuwi.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=paulkoning@comcast.net \
    /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