This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch 1/2] Make values more lazy if possible
- From: Doug Evans <dje at google dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, gdb-patches at sourceware dot org, Andrew Burgess <aburgess at broadcom dot com>
- Date: Mon, 10 Jan 2011 09:27:42 -0800
- Subject: Re: [patch 1/2] Make values more lazy if possible
- References: <20110106120312.GB32416@host1.dyn.jankratochvil.net> <m3d3o9rebt.fsf@fleche.redhat.com>
On Thu, Jan 6, 2011 at 12:01 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> Jan> currently sometimes value->contents is allocated despite
> Jan> value->lazy is set.
>
> I looked through this and I think it seems reasonable.
>
> It makes me wonder why we need allocate_value at all, though
> I assume I'm forgetting something :)
I was thinking the same about set_value_lazy.
It's continued presence may make this issue recur.