On Mon, Oct 18, 2021 at 12:59:35PM +0200, John Paul Adrian Glaubitz wrote:
> On 10/18/21 12:51, Antonio Terceiro wrote:
> >> 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
>
> Hmm, both were built with glibc 2.32-4.
I don't think we are on the right track here. I need to read the failing
test correctly. this "test case" alone is bogus, as
ruby -e 'END {Process.kill :SEGV, $$}'
is _expected_ to segfault, i.e. the process is sending a SEGV signal to
itself. This test case is not complete.
Attachment:
signature.asc
Description: PGP signature