[DRE-maint] Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault

Antonio Terceiro terceiro at debian.org
Sun Oct 17 19:57:04 BST 2021


Source: ruby3.0
Version: 3.0.2-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
X-Debbugs-CC: debian-powerpc at lists.debian.org

I'm copying the debian-powerpc list to see if anyone can help.

ruby3.0 fails to build on ppc64el. 4 test cases results in Segmentation
faults.

I was able to reproduce this on the porter box, and the minimal test
case, inside a build source tree, is this:

./miniruby -e 'END {Process.kill :SEGV, $$}'

The actual build failures are:

>   1) Failure:
> TestBugReporter#test_bug_reporter_add [/<<PKGBUILDDIR>>/test/-ext-/bug_reporter/test_bug_reporter.rb:24]:
> pid 111637 killed by SIGSEGV (signal 11)
> | -:1: [BUG] Segmentation fault at 0x00000b880001b415
> | ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [powerpc64le-linux-gnu]
> | 
> | -- Control frame information -----------------------------------------------
> | c:0003 p:---- s:0012 e:000011 CFUNC  :kill
> | c:0002 p:0021 s:0006 e:000005 EVAL   -:1 [FINISH]
> | c:0001 p:0000 s:0003 E:0000c0 (none) [FINISH]
> | 
> | -- Ruby level backtrace information ----------------------------------------
> | -:1:in `<main>'
> | -:1:in `kill'
> | 
> | -- C level backtrace information -------------------------------------------
> .
> 
> 1. [2/2] Assertion for "stderr"
>    | Expected /Sample bug reporter: 12345/
>    | to match
>    |   "-- Control frame information -----------------------------------------------\n"+
>    |   "c:0003 p:---- s:0012 e:000011 CFUNC  :kill\n"+
>    |   "c:0002 p:0021 s:0006 e:000005 EVAL   -:1 [FINISH]\n"+
>    |   "c:0001 p:0000 s:0003 E:0000c0 (none) [FINISH]\n\n"+
>    |   "-- Ruby level backtrace information ----------------------------------------\n"+
>    |   "-:1:in `<main>'\n"+
>    |   "-:1:in `kill'\n\n"+
>    |   "-- C level backtrace information -------------------------------------------\n"
>    | after 4 patterns with 125 characters.
> 
>   2) Failure:
> TestRubyOptions#test_segv_loaded_features [/<<PKGBUILDDIR>>/test/ruby/test_rubyoptions.rb:757]:
> pid 119318 killed by SIGSEGV (signal 11)
> | -e:1: [BUG] Segmentation fault at 0x00000b880001d216
> | ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [powerpc64le-linux-gnu]
> | 
> | -- Control frame information -----------------------------------------------
> | c:0003 p:---- s:0012 e:000011 CFUNC  :kill
> | c:0002 p:0016 s:0006 e:000005 BLOCK  -e:1 [FINISH]
> | c:0001 p:0000 s:0003 E:001240 (none) [FINISH]
> | 
> | -- Ruby level backtrace information ----------------------------------------
> | -e:1:in `block in <main>'
> | -e:1:in `kill'
> | 
> | -- C level backtrace information -------------------------------------------
> .
> 
> 1. [2/2] Assertion for "stderr"
>    | <""> expected but was
>    | <"-- C level backtrace information -------------------------------------------\n">.
> 
>   3) Failure:
> TestRubyOptions#test_segv_setproctitle [/<<PKGBUILDDIR>>/test/ruby/test_rubyoptions.rb:771]:
> pid 119319 killed by SIGSEGV (signal 11)
> | -e:1: [BUG] Segmentation fault at 0x00000b880001d217
> | ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [powerpc64le-linux-gnu]
> | 
> | -- Control frame information -----------------------------------------------
> | c:0003 p:---- s:0012 e:000011 CFUNC  :kill
> | c:0002 p:0029 s:0006 e:000005 EVAL   -e:1 [FINISH]
> | c:0001 p:0000 s:0003 E:001a80 (none) [FINISH]
> | 
> | -- Ruby level backtrace information ----------------------------------------
> | -e:1:in `<main>'
> | -e:1:in `kill'
> | 
> | -- C level backtrace information -------------------------------------------
> .
> 
> 1. [2/2] Assertion for "stderr"
>    | <""> expected but was
>    | <"-- C level backtrace information -------------------------------------------\n">.
> 
>   4) Failure:
> TestRubyOptions#test_segv_test [/<<PKGBUILDDIR>>/test/ruby/test_rubyoptions.rb:751]:
> pid 119320 killed by SIGSEGV (signal 11)
> | -e:1: [BUG] Segmentation fault at 0x00000b880001d218
> | ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [powerpc64le-linux-gnu]
> | 
> | -- Control frame information -----------------------------------------------
> | c:0003 p:---- s:0012 e:000011 CFUNC  :kill
> | c:0002 p:0015 s:0006 e:000005 EVAL   -e:1 [FINISH]
> | c:0001 p:0000 s:0003 E:001870 (none) [FINISH]
> | 
> | -- Ruby level backtrace information ----------------------------------------
> | -e:1:in `<main>'
> | -e:1:in `kill'
> | 
> | -- C level backtrace information -------------------------------------------
> .
> 
> 1. [2/2] Assertion for "stderr"
>    | <""> expected but was
>    | <"-- C level backtrace information -------------------------------------------\n">.
> 
> Finished tests in 784.310094s, 26.8248 tests/s, 3410.9162 assertions/s.
> 21039 tests, 2675216 assertions, 4 failures, 0 errors, 107 skips
> 
> ruby -v: ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [powerpc64le-linux-gnu]
> make[2]: *** [uncommon.mk:800: yes-test-all] Error 4


The full build log is available from:
http://qa-logs.debian.net/2021/10/17/ruby3.0.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20211017/c2239cb4/attachment-0001.sig>


More information about the Pkg-ruby-extras-maintainers mailing list