https://bugs.kde.org/show_bug.cgi?id=384732
Bug ID: 384732
Summary: posix_spawn with glibc 2.25 causes an assertion
Product: valgrind
Version: 3.13.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: d...@innovaphone.com
Target Milestone: ---
Created attachment 107867
--> https://bugs.kde.org/attachment.cgi?id=107867&action=edit
c code to reproduce the issue.
I'm encounting an ASSERT inside the glibc 2.25, if I run the test app where
posix_spawnp (or posix_spawn, doesn't matter), is called:
../sysdeps/unix/sysv/linux/spawni.c:360: __spawnix: Assertion `ec >= 0' failed.
Using glibc 2.24 works fine. valgrind 3.12/3.13 doesn't matter, although I
didn't test an SVN build, just official builds.
I get this assertion on i386 and arm builds (buildroot environment).
I call the binary like this, without any more options:
valgrind ./test
Without valgrind, the code is executed without problems.
Greetings,
Daniel
--
You are receiving this mail because:
You are watching all bug changes.
