[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
testing on sh4 hardware?
From: |
Bruno Haible |
Subject: |
testing on sh4 hardware? |
Date: |
Sat, 01 Jul 2017 17:43:32 +0200 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-81-generic; KDE/5.18.0; x86_64; ; ) |
Hi,
Does someone have access to sh4 hardware and could test gnulib on sh4-linux?
With qemu-sh4 and glibc-2.23, I'm seeing a couple of worrisome test failures:
FAIL: test-lock
===============
Starting test_lock ...test-lock: pthread_mutex_lock.c:81: __pthread_mutex_lock:
Assertion `mutex->__data.__owner == 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
FAIL test-lock (exit status: 134)
FAIL: test-pread.sh
===================
../../gltests/test-pread.c:61: assertion 'pread (fd, &byte_buf, 1, i) == 1'
failed
qemu: uncaught target signal 6 (Aborted) - core dumped
../../gltests/test-pread.sh: line 5: 5058 Done :
5059 Aborted (core dumped) | test-pread
FAIL test-pread.sh (exit status: 1)
FAIL: test-pwrite.sh
====================
../../gltests/test-pwrite.c:77: assertion 'strcmp ("W1W3W5W7W9",buf) == 0'
failed
qemu: uncaught target signal 6 (Aborted) - core dumped
../../gltests/test-pwrite.sh: line 5: 5346 Aborted (core
dumped) test-pwrite
FAIL test-pwrite.sh (exit status: 1)
FAIL: test-tls
==============
Starting test_tls ...FAIL test-tls (exit status: 143)
It is glibc's threading that is so broken on this platform, or is it a bug in
qemu?
Bruno
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- testing on sh4 hardware?,
Bruno Haible <=