This is the mail archive of the
dwarf2@corp.sgi.com
mailing list for the dwarf2 project.
Re: location lists
- To: todd dot allen at ccur dot com, Michael Eager <eager at eagercon dot com>
- Subject: Re: location lists
- From: David B Anderson <davea at quasar dot engr dot sgi dot com>
- Date: Thu, 8 Mar 2001 14:42:31 -0800 (PST)
- Cc: dwarf2 <dwarf2 at corp dot sgi dot com>
- References: <200103081550.f28Fo8302279@toad.ccur.com>
- Reply-To: David B Anderson <davea at quasar dot engr dot sgi dot com>
|> Right here is where you lose me. DWARF doesn't describe references to
|> global symbols; it only describe declarations & definitions. So, how can
|> a debugger know if there is a reference in the current context? Surely
|> you're not talking about requiring a vendor extension to get this right?
|> Maybe you're talking about deducing the presence of a reference by looking
|> for a replicated global definition (which is problematic for Ada's
|> describe-an-object-once-only approach)?
|
|If there is a reference to a variable in the current context, there must
|be a declaration.
Normally (to save space) declarations are ignored in dwarf
(except in special cases, mentioned in the dwarf2 spec).
The suggestion is that a non-defining
declaration have a location list?
But section 4.1 (draft 5 page 53) says non-defining declarations
are not allowed to have a location attribute (bullet 3.).
(the words are just a tiny bit soft, but that's how I read it).
davea@sgi.com