This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [WIP]: LOC_COMPUTED and LOC_COMPUTED_ARG
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: Daniel Berlin <dan at dberlin dot org>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Sat, 06 Apr 2002 20:23:26 -0500
- Subject: Re: [WIP]: LOC_COMPUTED and LOC_COMPUTED_ARG
- References: <Pine.LNX.4.44.0204061936130.28028-100000@dberlin.org>
> and
>>
>
>> > - the frame base address (for DW_OP_fbreg)
>> >
>> >
>> > Not possible.
>> > the frame base can be a location list.
>> > That's why it pulls it out of the frame function on the fly.
>
>>
>> Something I've never understood. Shouldn't frame_base be stored in
>> frame->base as part of the initial frame creation. Hence avoiding this
>> recursion?
>
>
> Theoretically you could, but it's sort of pointless.
> You still end up doing the same lookup.
> It also hides the code, since the code to create frames is nowhere
> near the dwarf2 reader.
I'm still missing something. If dwarf2 info isn't used to compute
frame->base (and frame->prev->pc) where are the values comming from?
Andrew