I pushed a patch for test 114.

On old libc there seems to be a race condition with stdio and fork().

I could reproduce the problem (after about 1000 runs) on i686 with old fedora release.

I can not reproduce the problem on my current x86_64 machine with latest fedora.

Herman

On 11/10/20 7:21 AM, Christian Jullien wrote:

Hi Herman,

I quickly replaced __APPLE__ by __clang__ in 114 test but, as this test is not reproducible, I can’t say it is the right fix to apply.

I ran changes locally on Debian x86_64 and RPi Debian 32 which passed 114 test.

Is it annoyed to have do_fork thread always executed?

*From:*Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] *On Behalf Of *Christian Jullien
*Sent:* Monday, November 09, 2020 21:24
*To:* jull...@eligis.com; tinycc-devel@nongnu.org
*Cc:* 'Herman ten Brugge'
*Subject:* [Tinycc-devel] Seg fault with test 114 on Debian x64

Hi again Herman,

I continue to test mod with your latest patch on the (many) machines I have.

This time, it is a Debian 10.6 x86_64 fully up to date and, guess what?, it fails on test  114 with clang 7.0, (gcc worked).

See log below:

jullien@debian64:~$ uname -a

Linux debian64 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1 (2020-10-18) x86_64 GNU/Linux

jullien@debian64:~$ clang -v

clang version 7.0.1-8+deb10u2 (tags/RELEASE_701/final)

Target: x86_64-pc-linux-gnu

Thread model: posix

InstalledDir: /usr/bin

Found candidate GCC installation: /usr/bin/../lib/gcc/i686-linux-gnu/6

Found candidate GCC installation: /usr/bin/../lib/gcc/i686-linux-gnu/6.3.0

Found candidate GCC installation: /usr/bin/../lib/gcc/i686-linux-gnu/8

Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/6

Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/6.3.0

Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7

Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7.4.0

Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8

Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6

Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6.3.0

Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/8

Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6

Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.3.0

Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7

Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.4.0

Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8

Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8

Candidate multilib: .;@m64

Candidate multilib: 32;@m32

Candidate multilib: x32;@mx32

Selected multilib: .;@m64

=== Bootstrapping with clang static

Binary directory    /usr/local/bin

TinyCC directory /usr/local/lib/tcc

Library directory   /usr/local/lib

Include directory /usr/local/include

Manual directory /usr/local/share/man

Info directory /usr/local/share/info

Doc directory /usr/local/share/doc

Source path /home/jullien/tinycc

C compiler          clang (7.0)

Target OS           Linux

CPU x86_64

Triplet x86_64-linux-gnu

Config              strip

Test: 114_bound_signal...

--- 114_bound_signal.expect 2020-11-09 21:10:32.444251010 +0100

+++ 114_bound_signal.output 2020-11-09 21:11:34.000089207 +0100

@@ -1,2 +1,3 @@

start

end

+end

make[3]: *** [Makefile:117: 114_bound_signal.test] Error 1

Test: 115_bound_setjmp...


_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to