Re: [Dwarf-Discuss] Default Location List Entry Issue 130121.1

2014-04-22 Thread Michael Eager
On 04/22/14 03:57, Mark Wielaard wrote: Assuming the consumer is interested in "the object is not available for the portion of the range that is not covered" property of the location list then it looks like if the producer uses a default location list entry that information is no longer availabl

Re: [Dwarf-Discuss] Default Location List Entry Issue 130121.1

2014-04-22 Thread Mark Wielaard
Hi Paul, On Thu, 2014-04-03 at 13:46 +, Robinson, Paul wrote: > Consider a subprogram with a local stack-allocated variable. In the > simple case, a simple location description gives that location, and > of course it's valid for the address-range of the containing subprogram. > > The compile

[Dwarf-Discuss] D.4 Member Function Example

2014-04-22 Thread Mark Wielaard
Hi, I was looking at the D.4 Member Function Example and noticed it flags member functions that don't return a value with a DW_AT_type pointing to a DW_TAG_unspecified_type with name "void". I haven't encountered producers that do this and it seems 5.5.7 Member Function Entries imply that DW_TAG_s