Re: [Dwarf-Discuss] .debug_addr entry plus offset

2020-09-15 Thread David Blaikie via Dwarf-Discuss
On Tue, Sep 15, 2020 at 2:47 PM Greg Clayton via Dwarf-Discuss wrote: > > One simple approach would be to be able to represent a DW_AT_low_pc with a > DW_FORM_data encoding just like the DW_AT_high_pc does when it is an offset > from the DW_AT_low_pc. I'm not sure this would catch all the

Re: [Dwarf-Discuss] .debug_addr entry plus offset

2020-09-15 Thread Greg Clayton via Dwarf-Discuss
One simple approach would be to be able to represent a DW_AT_low_pc with a DW_FORM_data encoding just like the DW_AT_high_pc does when it is an offset from the DW_AT_low_pc. The value of the DW_AT_low_pc would be an offset from either: 1 - the parent DIE's DW_AT_low_pc (which itself might need

Re: [Dwarf-Discuss] .debug_addr entry plus offset

2020-09-15 Thread David Blaikie via Dwarf-Discuss
On Tue, Sep 15, 2020 at 10:13 AM Robinson, Paul via Dwarf-Discuss wrote: > > David Blaikie has brought this up with me (or in conversations that > I observed) a couple of times: Thanks for bringing this up! Not sure if I've raised this on dwarf-discuss specifically before.. ah, yeah, 3 years

[Dwarf-Discuss] .debug_addr entry plus offset

2020-09-15 Thread Robinson, Paul via Dwarf-Discuss
David Blaikie has brought this up with me (or in conversations that I observed) a couple of times: It's common to want to refer to a particular address plus an offset, for example for DW_AT_low_pc or DW_AT_ranges to describe a lexical block or inlined subprogram within another subprogram.