Bug #18131: addr2line.c: Some inlined functions mistakenly shown

• Status: Open
• Assignee: -
• Target version: -
• ruby -v: ruby 3.1.0dev (2021-08-24T15:36:23Z master 716624660b) [powerpc64le-linux]
• Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN

[xtkoba (Tee KOBAYASHI)]

What is observed in ppc64le CI (pathnames edited for readability):

-- C level backtrace information -------------------------------------------
/home/xxx/ruby/ruby(rb_vm_bugreport+0x198) [0x6430d199028] vm_dump.c:759
/home/xxx/ruby/ruby(ibf_load_small_value+0x78) [0x6430cf011c8] error.c:815
/home/xxx/ruby/ruby(ibf_load_iseq_each) compile.c:11650
/home/xxx/ruby/ruby(vm_respond_to) compile.c:12594
/home/xxx/ruby/ruby(rb_ec_obj_respond_to) vm_method.c:2576
/home/xxx/ruby/ruby(rb_obj_respond_to) vm_method.c:2569
/home/xxx/ruby/ruby(rb_bug_for_fatal_signal) vm_method.c:2584
/home/xxx/ruby/ruby(sigsegv+0x64) [0x6430d0bb954] signal.c:961
linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0) [0x795f1d6304c8]
/home/xxx/ruby/ruby(rb_ary_push+0x2c) [0x6430d1b31cc] array.c:1313
(...)

Here, 6 functions are shown for address 0x6430cf011c8, of which only rb_bug_for_fatal_signal is valid.

I have not yet come up with how to fix this, but I suspect this is partially due to ranges_include in addr2line.c not handling DW_AT_entry_pc at all.