Hi -
> > But please don't sent HTML email. It will make DKIM verification of
> > your email impossible.
>
> Hmm - how does HTML email relate to/interfere with DKIM verification?
The public-inbox copy of the email would drop the HTML attachment,
invalidating any attached crypto signatures.
-
Hi -
> I understand the desire for each particular vendor opcode to have a
> semantic meaning that is fixed throughout time. [...] Does this
> continue to be an goal for DWARF6? Whether or not this is true, we
> should make this explicit. If not, it would provide an opportunity
> for tool
Hi -
> We have seen GSYM files up to 20x smaller than the DWARF file, which
> to be fair often includes all other sections (.text, .data, etc).
What information is lost?
- FChE
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
Hi, Andrew -
On Tue, Mar 09, 2021 at 10:05:04AM -0500, Andrew Cagney via Dwarf-Discuss wrote:
> [...]
> This means that:
> - for simple objects, local functions; and
> - with link-time-optimization, everything except library interface functions
> are fair game for ABI non-compliant call
Hi -
> Can you explain this more?
>
> DWARF handles the situation where part of a variable is in memory and part
> in a register or in multiple registers. When would you have a variable
> which was in multiple address spaces?
Remember the "how can a debugger WRITE safely to variables"
Hi -
> With split lifetimes, the debugger can ask the user which of the
> lifetimes the user wants to set. [...] ...based on looking at the
> 'assign' location list.
Yup, those are reasonable user-interface ideas. (I'm not sure we'd
require a whole separate location list, versus tagging the
Hi -
> While dwarfdump has 'check the DWARF' options available the
> location list overlap test is not done at all. The -kl option suggests
> it does loclist checking, but its checking is rather superficial.
Note that one should not present these overlaps as -errors- (because
they may be
Hi -
> > - ... and undoubtedly other complications exist!
>
> Interesting question.
Thanks!
We have been thinking in similar directions generally as y'all.
> Complication 2: The compiler reuses variable locations at the same PC. This
> seems to be a compiler bug.
(Actually, this could be
Hi -
I have a question about variable location lists, but not their
encoding, the use they are suitable for. The basic debugging scenario
is just reading variable values, for which this is fine, especially
when high-quality compilers emit exquisitely detailed data for their
optimized code.
But
