I’m just a new lurker here, so maybe this is obvious…
Is the string part of the programmatic interface? Or just a comment?
Does the same numeric code always have the same string?
If the same numeric code can have different strings, then the string
represents a specialization of the error code? I
My main concern was that *if* strings are added, there's some
clear documentation about the relationship between the string
and the number to explain what's going on. Based on other
emails in this thread it seems like the numbers are so unreliable that
it might not be worth the trouble.
What abou
Have you guys considered going all the way and recording multiple layers
of line information for the same range of instructions, and allowing the user
to jump up and down through the not-really-there function calls? That seems
like a very usefuil features for looking at optimized code. You’d nee
> On Sep 14, 2017, at 3:32 PM, Jim Ingham wrote:
>
> This is supported (admittedly a little awkwardly) in DWARF with the
> DW_TAG_inline_subroutine DIE's in the debug_info section of the DWARF. They
> can expresses the nesting fully.
>
Sorry for the delay in responding.
For now, I don’t
> On Sep 22, 2017, at 4:18 PM, Robinson, Paul wrote:
>
> For contiguous ranges described by low_pc/hi_pc attribute
> pairs, the hi_pc can be a constant for the length, so you save
> a little space and a relocation. I think that’s in DWARF 4.
>
> DWARF 5 redid the ranges section, to do a lot mo
