You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support cross-CU DW_FORM_ref_addr in addr2line's abstract_origin
Under GCC LTO the C-level backtrace in a crash report printed only bare
hex addresses (e.g. "ruby(0x...) [0x...]") for every ruby frame, even
though gdb resolved the same binary fine.
The concrete out-of-line function DIE carries DW_AT_low_pc, so the crash
PC matches a DIE and the DWARF parse "succeeds"; but its name is reached
only through a DW_AT_abstract_origin encoded as DW_FORM_ref_addr, a
section-relative reference into another CU (LTO emits the concrete and
abstract instances in separate CUs). addr2line.c handled the CU-relative
ref forms but had DW_FORM_ref_addr as "not supported yet".
[Bug #22188]
0 commit comments