[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#710439: marked as done (pixman fails testsuite on powerpc due to glibc)



Your message dated Tue, 6 Sep 2022 21:21:58 +0200
with message-id <Yxed1nFNjnqy4h7d@aurel32.net>
and subject line Re: More info
has caused the Debian Bug report #710439,
regarding pixman fails testsuite on powerpc due to glibc
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
710439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710439
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: eglibc
Version: 2.13-38

When I try to build pixman (0.26.0-4) in my powerpc wheezy chroot,
the testsuite fails.

The failure usually looks like:

*** glibc detected *** /tmp/pixman-0.26.0/build/test/.libs/lt-scaling-test: corrupted double-linked list: 0x10068e80 ***
======= Backtrace: =========
/lib/powerpc-linux-gnu/libc.so.6(+0x86ef4)[0xfd4fef4]
/lib/powerpc-linux-gnu/libc.so.6(+0x88b24)[0xfd51b24]
/lib/powerpc-linux-gnu/libc.so.6(cfree+0x8c)[0xfd554cc]
/tmp/pixman-0.26.0/build/test/.libs/lt-scaling-test[0x10001ba0]
/tmp/pixman-0.26.0/build/test/.libs/lt-scaling-test[0x100024dc]
/usr/lib/powerpc-linux-gnu/libgomp.so.1(+0xb5e0)[0xfe975e0]
/lib/powerpc-linux-gnu/libpthread.so.0(+0x67b0)[0xfe577b0]
/lib/powerpc-linux-gnu/libc.so.6(clone+0x84)[0xfdbd960]
======= Memory map: ========
00100000-00103000 r-xp 00000000 00:00 0                                  [vdso]
0fca0000-0fca8000 r-xp 00000000 fd:01 4211711                            /lib/powerpc-linux-gnu/librt-2.13.so
0fca8000-0fcb7000 ---p 00008000 fd:01 4211711                            /lib/powerpc-linux-gnu/librt-2.13.so
0fcb7000-0fcb8000 r--p 00007000 fd:01 4211711                            /lib/powerpc-linux-gnu/librt-2.13.so
0fcb8000-0fcb9000 rw-p 00008000 fd:01 4211711                            /lib/powerpc-linux-gnu/librt-2.13.so
0fcc9000-0fe39000 r-xp 00000000 fd:01 4211720                            /lib/powerpc-linux-gnu/libc-2.13.so
0fe39000-0fe3d000 r--p 00170000 fd:01 4211720                            /lib/powerpc-linux-gnu/libc-2.13.so
0fe3d000-0fe3e000 rw-p 00174000 fd:01 4211720                            /lib/powerpc-linux-gnu/libc-2.13.so
0fe3e000-0fe41000 rw-p 00000000 00:00 0 
0fe51000-0fe69000 r-xp 00000000 fd:01 4211733                            /lib/powerpc-linux-gnu/libpthread-2.13.so
...

Also:
*** glibc detected *** /tmp/pixman-0.26.0/build/test/.libs/lt-affine-test: corrupted double-linked list: 0x45f00760 ***
======= Backtrace: =========
/lib/powerpc-linux-gnu/libc.so.6(+0x86ef4)[0xfd4fef4]
/lib/powerpc-linux-gnu/libc.so.6(+0x88b24)[0xfd51b24]
/lib/powerpc-linux-gnu/libc.so.6(cfree+0x8c)[0xfd554cc]
/tmp/pixman-0.26.0/build/test/.libs/lt-affine-test[0x10001a0c]
/tmp/pixman-0.26.0/build/test/.libs/lt-affine-test[0x10002188]
/usr/lib/powerpc-linux-gnu/libgomp.so.1(+0xb5e0)[0xfe975e0]
/lib/powerpc-linux-gnu/libpthread.so.0(+0x67b0)[0xfe577b0]
/lib/powerpc-linux-gnu/libc.so.6(clone+0x84)[0xfdbd960]
======= Memory map: ========
...


If I install libc6 and libc6-dev 2.17-3, the problem goes away and all
tests pass.  Hence why I am assigning blame to glibc for this.

Of course this makes me rather concerned about the glibc in wheezy for
use on powerpc.

Any idea what could be broken in 2.13 and how to fix it, since I would
prefer to stick with stable.  A patch to 2.13 would seem rather preferable
for wheezy than having to start mixing in other bits, especially glibc.

I am building on an IBM p710 with 6 cores, so lots of parallelism is
certainly possible and likely, which may help to trigger bugs like this.

I would think this qualifies as a severity for FTBFS, even though it
isn't glibc that is failing to build, but it is causing other things to
fail to build.

-- 
Len Sorensen

--- End Message ---
--- Begin Message ---
Version: 2.17-1

On 2013-09-16 15:57, Lennart Sorensen wrote:
> So I have tried some more attempts.
> 
> If I disable vmx use in pixman, the crashes go away.
> If I disable use of openMP in pixman, the crashes go away.
> If I run on a power6 rather than power7, the crashes go away.
> If I use strace, the crashes go away.
> If I use gdb, the crashes go away.
> If I install libc 2.17 instead of 2.13 (without recompiling anything),
> the crashes go away.
> 
> So somehow it seems to be in interaction between vmx instructions and
> openMP on power7, probably to due with memory barriers (or lack of
> them somewhere between threads), with very specific timing (which gdb,
> strace both affect), which has either been fixed in libc 2.17, or the
> timing is somehow different again masking the problem.

Since the problem is not reproducible starting with glibc 2.17 and that
we do not support glibc 2.13 shipped (in Wheezy) anymore, I am closing
this bug.  Please feel free to reopen it if you can reproduce the
problem with recent versions.

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---

Reply to: