This is the mail archive of the archer@sourceware.org mailing list for the Archer 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 convenience functions that return GDB values cause segfault

From: Tom Tromey <tromey at redhat dot com>
To: Thiago Jung Bauermann <bauerman at br dot ibm dot com>
Cc: Jim Blandy <jimb at red-bean dot com>, archer at sourceware dot org
Date: Wed, 04 Feb 2009 11:06:04 -0700
Subject: Re: Python convenience functions that return GDB values cause segfault
References: <8f2776cb0902031709g55787f3are0b3c18d743a5827@mail.gmail.com><1233764550.14735.52.camel@localhost.localdomain>
Reply-to: Tom Tromey <tromey at redhat dot com>

>>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:

Thiago> I think it's better to return a copy of the value.

Yeah, I agree.

This thread, plus Paul's value-related memory leak note, makes me
wonder whether we ought to try to implement reference counting for
struct value.  It seems like a big project, though.

Tom

Follow-Ups:
- Re: Python convenience functions that return GDB values causesegfault
  - From: Daniel Jacobowitz

References:
- Python convenience functions that return GDB values cause segfault
  - From: Jim Blandy
- Re: Python convenience functions that return GDB values causesegfault
  - From: Thiago Jung Bauermann

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