This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB 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: [WIP]: LOC_COMPUTED and LOC_COMPUTED_ARG


> 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


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