Processing control commands:
> reopen -1
Bug #996724 {Done: Antonio Terceiro } [src:ruby3.0]
ruby3.0: FTBFS on ppc64el: Segmentation fault
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No
Control: reopen -1
Control: retitle -1 ruby3.0: Segmentation fault on ppc64el when compiled with
gcc-11
Control: severity -1 important
Hi,
On Sat, Oct 30, 2021 at 08:50:10AM +0200, Lucas Nussbaum wrote:
> Hi,
>
> On 30/10/21 at 00:13 +0200, Lucas Nussbaum wrote:
> > Hi,
> >
> > ruby 3.0 3.0.2-
Hi,
On 30/10/21 at 00:13 +0200, Lucas Nussbaum wrote:
> Hi,
>
> ruby 3.0 3.0.2-4:
> - builds fine in Debian stable
> - fails in unstable
> - builds fine in unstable snapshotted on 20210930T210616Z
> - fails in unstable snapshotted on 20211014T215029Z
I confirm that this is due to the switch from
Hi,
ruby 3.0 3.0.2-4:
- builds fine in Debian stable
- fails in unstable
- builds fine in unstable snapshotted on 20210930T210616Z
- fails in unstable snapshotted on 20211014T215029Z
The differences in terms of packages between the two last builds are:
14c14
< ii bash
On Mon, Oct 18, 2021 at 01:22:25PM +0200, John Paul Adrian Glaubitz wrote:
> On 10/18/21 13:16, Antonio Terceiro wrote:
> > 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, $$}
On 10/18/21 13:16, Antonio Terceiro wrote:
> 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
> itse
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 rec
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.
> 0x77a48f04 in kill () from /lib/powerpc
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
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/s
Hi!
On 10/17/21 21:47, John Paul Adrian Glaubitz wrote:
> Since ruby3.0 used to build fine on ppc64el in the past, the easiest way would
> be to just bisect the issue. I can give it a try and see if I can find the
> problematic commit.
Ah, so the last successful build was 3.0.2-2 and the first fa
Hello Antonio!
On 10/17/21 20:57, Antonio Terceiro wrote:
> 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
Source: ruby3.0
Version: 3.0.2-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
X-Debbugs-CC: debian-powe...@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
13 matches
Mail list logo
