[Bug libc/23239] elf/tst-latepthread test fails with GCC 8.1.0

carlos at redhat dot com sourceware-bugzilla@sourceware.org
Wed May 30 16:28:00 GMT 2018


https://sourceware.org/bugzilla/show_bug.cgi?id=23239

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com

--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #0)
> glibc 2.27 (with some patches backported in Gentoo), Binutils 2.30.
> With GCC 7.3.0, I get 2 test failures.
> With GCC 8.1.0, I get 3 test failures.
> The test which passes with GCC 7.3.0 and fails with GCC 8.1.0 is
> elf/tst-latepthread.
> 
> There are no recent changes in
> https://sourceware.org/git/?p=glibc.git;a=history;f=elf/tst-latepthread.c;
> hb=HEAD so probably this problem was not fixed in newer versions of glibc.
> 
> 
> elf/tst-latepthread.test-result contains:
> FAIL: elf/tst-latepthread
> original exit status 1
> 
> 
> elf/tst-latepthread.out contains:
> info: exit status: 139, message: 
> error: message does not contain expected string

Can you build with --enable-hardcoded-paths-in-tests, and then try to debug the
test that is failing and see where it fails?

The 139 is a SIGSEGV which is surprising, but might be a compiler bug. I
haven't seen this test fail.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Glibc-bugs mailing list