On 13.06.2016 22:59, Eric Wong wrote: > Mattia Rizzolo <mat...@debian.org> wrote: >> On Mon, Jun 13, 2016 at 10:40:51PM +0200, Helge Deller wrote: >>> Program received signal SIGSEGV, Segmentation fault. >>> [Switching to Thread 0xfa5dd480 (LWP 29258)] >>> mix_id_table_lookup (tbl=0x0, id=id@entry=3265, valp=valp@entry=0xfa55f248) >>> at id_table.c:1516 > > tbl=0x0 looks like a bug in Ruby; possibly GC-related. > >>> 1516 id_table.c: No such file or directory. >>> (gdb) bt >>> #0 mix_id_table_lookup (tbl=0x0, id=id@entry=3265, >>> valp=valp@entry=0xfa55f248) at id_table.c:1516 >>> #1 0xf9c91b04 in lookup_method_table (id=3265, klass=<optimized out>) at >>> vm_method.c:190 >>> #2 search_method (defined_class_ptr=<optimized out>, id=<optimized out>, >>> klass=<optimized out>) at vm_method.c:701 >>> #3 method_entry_get_without_cache (defined_class_ptr=<optimized out>, >>> id=<optimized out>, klass=<optimized out>) at vm_method.c:726 >>> #4 method_entry_get (klass=1134408, id=3265, id@entry=1134408, >>> defined_class_ptr=defined_class_ptr@entry=0xfa55f1c8) at vm_method.c:786 >>> #5 0xf9c94e90 in rb_callable_method_entry (klass=<optimized out>, >>> id=1134408, id@entry=4199936456) at vm_method.c:831 >>> #6 0xf9ca6048 in rb_search_method_entry (mid=4199936456, recv=1134408) at >>> vm_eval.c:573 >>> #7 rb_call0 (recv=1134408, mid=4199936456, argc=3265, argv=0xfa55f248, >>> scope=<optimized out>, self=<optimized out>) at vm_eval.c:343 >>> #8 0xf9ca6984 in rb_call (scope=CALL_FCALL, argv=<optimized out>, >>> argc=<optimized out>, mid=<optimized out>, recv=<optimized out>) at >>> vm_eval.c:637 >>> #9 rb_funcall (recv=<optimized out>, mid=<optimized out>, n=<optimized >>> out>) at vm_eval.c:835 >>> #10 0x00000000 in ?? () >>> Backtrace stopped: previous frame identical to this frame (corrupt stack?) >>> >>> I assume it's a problem in ruby2.3 itself, but since I'm no expert in >>> ruby2.3, is there anyone who might be able to help? >>> I can provide a login to a hppa box if necessary... > > Seems to be a ruby2.3 problem. > Does the ruby2.3 test suite work at all on hppa?
No idea (I'm no ruby expert). The last build log is here: https://buildd.debian.org/status/fetch.php?pkg=ruby2.3&arch=hppa&ver=2.3.1-2&stamp=1464615629 The log looks similar to x86_64, but I'm not sure if the test suite is run then. > Any other ruby libraries with similar problems? I think most ruby packages build sucessfully. In the package overview I find only 9 ruby packages which don't build: https://buildd.debian.org/status/architecture.php?a=hppa&suite=sid Helge
