Bug 387686 - valgrind-3.13.0 tests on Gentoo fail with glibc-2.26 (work with glibc-2.25).
Summary: valgrind-3.13.0 tests on Gentoo fail with glibc-2.26 (work with glibc-2.25).
Status: CLOSED NOT A BUG
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: 3.13.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-07 20:20 UTC by Austin English
Modified: 2017-12-11 23:58 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
test failures (3.83 KB, text/plain)
2017-12-07 20:20 UTC, Austin English 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Austin English 2017-12-07 20:20:36 UTC 
Created attachment 109247 [details]
test failures

Originally reported here:
https://bugs.gentoo.org/637488

the valgrind-3.13.0 unit tests fail on an unstable Gentoo machine. They work for me on my stable machine. Testing in a chroot, I was able to find that glibc is the source of the problem. The working machine has:
sys-libs/glibc-2.25-r9, while sys-libs/glibc-2.26-r3 is broken.
Comment 1 Austin English 2017-12-11 21:42:21 UTC 
My fault for not testing git first. This was already fixed, by:
2b5eab6a8db1b0487a3ad7fc4e7eeda6d3513626
Author: Mark Wielaard <mark@klomp.org>
Date:   Thu Jun 29 15:26:30 2017 +0000

    memcheck/tests: Use ucontext_t instead of struct ucontext
Comment 2 Austin English 2017-12-11 23:58:31 UTC 
Closing.