[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault



On Mon, Oct 18, 2021 at 10:00:42AM +0200, John Paul Adrian Glaubitz wrote:
> Hello!
> 
> On 10/17/21 21:50, John Paul Adrian Glaubitz wrote:
> > Ah, so the last successful build was 3.0.2-2 and the first failure was in 3.0.2-3,
> > the only difference being the mipsel patch to fix an unaligned access.
> > 
> > However, 3.0.2-2 was built with gcc-10:
> > 
> >> https://buildd.debian.org/status/fetch.php?pkg=ruby3.0&arch=ppc64el&ver=3.0.2-2&stamp=1633362713&raw=0
> > 
> > while 3.0.2-3 was built with gcc-11:
> > 
> >> https://buildd.debian.org/status/fetch.php?pkg=ruby3.0&arch=ppc64el&ver=3.0.2-3&stamp=1634169532&raw=0
> > 
> > So, first we should try building with gcc-10 and see if that makes a difference.
> 
> I have tested the build with gcc-10 but the problem remains, so it's not a compiler
> issue. Dropping the patch rand_init-fix-off-by-one-error.patch that was introduced
> with 3.0.2-3 doesn't help either.
> 
> So, we need a backtrace to see where the crash actually happens. I assume it's in one
> of the build dependencies.

it happens in glibc:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7a48f04 in kill () from /lib/powerpc64le-linux-gnu/libc.so.6

#0  0x00007ffff7a48f04 in kill () from /lib/powerpc64le-linux-gnu/libc.so.6
#1  0x000000010023a8ec in rb_f_kill (argc=<optimized out>, argv=<optimized out>) at signal.c:481
#2  0x00000001001d0608 in proc_rb_f_kill (c=<optimized out>, v=<optimized out>, _=<optimized out>) at process.c:8605
#3  0x00000001002bd848 in ractor_safe_call_cfunc_m1 (recv=<optimized out>, argc=<optimized out>, argv=<optimized out>, func=<optimized out>) at vm_insnhelper.c:2736
#4  0x00000001002d2e6c in vm_call_cfunc_with_frame (ec=0x100453ad0, reg_cfp=0x7ffff79effa0, calling=<optimized out>) at vm_insnhelper.c:2926
#5  0x00000001002d5bb4 in vm_sendish (ec=0x100453ad0, reg_cfp=0x7ffff79effa0, cd=0x1005a0960, block_handler=<optimized out>, method_explorer=<optimized out>) at vm_callinfo.h:336
#6  0x00000001002da06c in vm_exec_core (ec=0x100453ad0, initial=<optimized out>, initial@entry=0) at insns.def:789
#7  0x00000001002dfcb0 in rb_vm_exec (ec=0x100453ad0, mjit_enable_p=<optimized out>) at vm.c:2172
#8  0x00000001002e5d7c in invoke_block (captured=<optimized out>, captured=<optimized out>, opt_pc=<optimized out>, type=<optimized out>, cref=0x0, self=4300276880, iseq=0x10046a478, ec=0x100453ad0) at vm.c:1263
#9  invoke_iseq_block_from_c (me=0x0, is_lambda=0, cref=0x0, passed_block_handler=0, kw_splat=0, argv=0x10046a280, argc=0, self=4300276880, captured=<optimized out>, ec=0x100453ad0) at vm.c:1335
#10 invoke_block_from_c_proc (me=0x0, is_lambda=<optimized out>, passed_block_handler=0, kw_splat=0, argv=0x10046a280, argc=0, self=4300276880, proc=<optimized out>, ec=0x100453ad0) at vm.c:1435
#11 vm_invoke_proc (ec=0x100453ad0, proc=<optimized out>, self=4300276880, argc=<optimized out>, argv=0x10046a280, kw_splat=<optimized out>, passed_block_handler=0) at vm.c:1464
#12 0x00000001001c8ffc in rb_proc_call (self=<optimized out>, args=<optimized out>) at proc.c:986
#13 0x00000001000c9cb0 in rb_call_end_proc (data=4299596440) at eval_jump.c:13
#14 0x00000001000c9d64 in exec_end_procs_chain (procs=procs@entry=0x10043a750 <end_procs>, errp=errp@entry=0x100453b48) at eval_jump.c:105
#15 0x00000001000cf9fc in rb_ec_exec_end_proc (ec=ec@entry=0x100453ad0) at eval_jump.c:120
#16 0x00000001000cfd84 in rb_ec_teardown (ec=ec@entry=0x100453ad0) at eval.c:175
#17 0x00000001000d0068 in rb_ec_cleanup (ec=ec@entry=0x100453ad0, ex=<optimized out>) at eval.c:243
#18 0x00000001000d0598 in ruby_run_node (n=0x10046a5b8) at eval.c:375
#19 0x000000010002aaa8 in main (argc=<optimized out>, argv=<optimized out>) at ./main.c:50

Attachment: signature.asc
Description: PGP signature


Reply to: