Re: Python: fetch value when building gdb.Value object

Tom Tromey
2011-10-20T15:04:00Z

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