This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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

From: Tom Tromey <tromey at redhat dot com>
To: Paul Koning <paulkoning at comcast dot net>
Cc: gdb-patches at sourceware dot org
Date: Wed, 19 Oct 2011 14:51:41 -0600
Subject: Re: Python: fetch value when building gdb.Value object
References: <36B29E9D-F2B3-446F-AF8A-97254A3AAEE2@comcast.net> <m3y5x0pxqg.fsf@fleche.redhat.com> <21467A42-84A3-4DFD-83A9-28FFFB0A5C7F@comcast.net> <m3y5wncpe0.fsf@fleche.redhat.com> <2F165381-183F-471F-8F55-457F08E6B008@comcast.net>

>>>>> "Paul" == Paul Koning <paulkoning@comcast.net> writes:

Paul> At this point the change has been approved and committed (that
Paul> happened before your comments arrived).  So I guess we have a question
Paul> of whether to change it back.

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

Tom

Follow-Ups:
- Re: Python: fetch value when building gdb.Value object
  - From: Paul Koning

References:
- Re: Python: fetch value when building gdb.Value object
  - From: Tom Tromey
- Re: Python: fetch value when building gdb.Value object
  - From: Paul Koning
- Re: Python: fetch value when building gdb.Value object
  - From: Tom Tromey
- Re: Python: fetch value when building gdb.Value object
  - From: Paul Koning

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]