On Fri, Mar 19, 2021 at 9:34 AM Samy Al Bahra wrote:
> Hi David,
>
> Sorry I'm a bit late to the game.
>
No worries at all - appreciate any/all perspectives/data here, for sure!
> On the value of having .debug_aranges and the performance impact:
>
> Our debugger was designed for performance an
Hi Greg,
We currently use a similar format for server-side symbolication where
static analysis is not being performed (for example, when we ingest core
dumps / minidump directly on the backend) with similar design goals, it was
inspired by Breakpad's sym and includes similar extensions for inline
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
http://lis
> On Mar 19, 2021, at 9:33 AM, Samy Al Bahra via Dwarf-Discuss
> wrote:
>
> Hi David,
>
> Sorry I'm a bit late to the game. On the value of having .debug_aranges and
> the performance impact:
>
> Our debugger was designed for performance and does end to end lazy evaluation
> (down to the D
Hi David,
Sorry I'm a bit late to the game. On the value of having .debug_aranges and
the performance impact:
Our debugger was designed for performance and does end to end lazy
evaluation (down to the DIE). This is quite old (excuse the formatting) but
numbers are here:
https://engineering.backtr
