Displaying 3 results from an estimated 3 matches for "debug_line_address".
2017 Nov 28
2
[LLD] Slow callstacks in gdb
...MIT_MACROS' redefined at...
> Member function "~basic_istream" (offset 28792309) is virtual but the
> vtable offset is not specified...
>
>
>
> Maybe gdb needs to fall back to slower line number resolution because e.g.
> low and high bounds cannot be retrieved and debug_line_address is 0?
It is hard to know without a reproducible. I tried gdb on clang itself
build with both clang and gcc and linked with gold and lld. I could not
reproduce the slowdown, but I was using trunk lld.
Cheers,
Rafael
2017 Nov 27
2
[LLD] Slow callstacks in gdb
Is the program being built by gcc or clang?
Cheers,
Rafael
Rafael Avila de Espindola <rafael.espindola at gmail.com> writes:
> Martin Richtarsky via llvm-dev <llvm-dev at lists.llvm.org> writes:
>
>> Hi,
>>
>> for programs linked with lld it's substantially slower to get callstacks
>> in gdb, in comparison to gold-linked programs. Two measurements:
2017 Dec 02
2
[LLD] Slow callstacks in gdb
Martin Richtarsky <s at martinien.de> writes:
> Rafael Avila de Espindola wrote :
>>> Maybe gdb needs to fall back to slower line number resolution because
>>> e.g.
>>> low and high bounds cannot be retrieved and debug_line_address is 0?
>>
>> It is hard to know without a reproducible. I tried gdb on clang itself
>> build with both clang and gcc and linked with gold and lld. I could not
>> reproduce the slowdown, but I was using trunk lld.
>
> I will retry with clang trunk, when it reproduces I w...