Ruby Issue Tracking System

07/02/2018

07:21 PM Ruby Bug #14883: Ruby 2.5 Fails to Build on PowerPC 32-bit (BE)

Bingo. It is also an issue for the systemd-nspawn container indeed.
systemd-nspawn have used a libseccomp whitelist instead of a blacklist by default since last year.
`rt_sigprocmask()` & `sigprocmask()` are on the whitelist, but `sw... lion (Daming Yang)

03:51 PM Ruby Bug #14883: Ruby 2.5 Fails to Build on PowerPC 32-bit (BE)

contd.
When it comes to a glibc function `getcontext()`, 'the root issue' of the bug, we can check it in this way:
~~~c
// cat lion_getcontext.c
#include <ucontext.h>
#include <errno.h>
int main() {
ucontext_t c;
if (... lion (Daming Yang)

03:07 PM Ruby Bug #14883: Ruby 2.5 Fails to Build on PowerPC 32-bit (BE)

I did some further investigation. It is a little bit longer story than I thought.
Firstly, the callstacks in Ruby shows that:
~~~
...
/root/ruby/lib/rdoc/parser/ripper_state_lex.rb:594:in `parse'
/root/ruby/lib/rdoc/parser/ripper_... lion (Daming Yang)

01:18 PM Ruby Bug #14883: Ruby 2.5 Fails to Build on PowerPC 32-bit (BE)

naruse (Yui NARUSE) wrote:
> Your build/SEGV log doesn't have the essential part of the crash log.
Bai's friend here. The missing part of the crash log: https://pastebin.aosc.io/paste/fBNM~Lr~C4vfsvHCpmPJOA
lion (Daming Yang)