Re: [PATCH 7/9] gdb: remove VALUE_NEXT_FRAME_ID, add value::next_frame_id

Tom Tromey
2023-12-22T16:51:32Z

>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:

Simon> Remove VALUE_NEXT_FRAME_ID, replace it with a method on struct value. Set
Simon> `m_location.reg.next_frame_id` directly from value::allocate_register_lazy,
Simon> which is fine because allocate_register_lazy is a static creation
Simon> function for struct value.

I looks like every user except value::fetch_lazy_register actually
immediatley calls find_frame_by_id with the result; so I wonder if this
should just return a frame_info_ptr instead.

BTW thank you for doing this, I'm happy to see VALUE_NEXT_FRAME_ID go away.

Tom