Variable objects laziness
Vladimir Prus
ghost@cs.msu.su
Mon Dec 4 19:27:00 GMT 2006
Daniel Jacobowitz wrote:
> On Sat, Nov 18, 2006 at 12:48:05PM +0300, Vladimir Prus wrote:
>> Daniel Jacobowitz wrote:
>>
>> >> + rather value_contents, will take care of this.
>> >> + It might throw, but unlike var-update for -var-assign
>> >> + there's just one variable we're working it, so we don't
>> >> + need to catch the exception here. */
>> >
>> > Wait, what? gdb_value_assign will never throw. value_contents
>> > might, but gdb_value_assign will catch it.
>>
>> Yep, confused gdb_value_assign with value_assign.
>>
>> Updated patch attached. I also attach the delta to the previous patch.
>
> This version is OK now (for HEAD only). Thanks for your patience.
> The frozen varobj patch had some further discussion; I'll have to
> get back to it, but I'm afraid not today. Poke me if I haven't done it
> in a few days, please.
*POKE*.
- Volodya
More information about the Gdb-patches
mailing list