https://bugs.kde.org/show_bug.cgi?id=450437
--- Comment #8 from Mark Wielaard <m...@klomp.org> ---
commit 8eb547054a051a00742b1b9e1b381015fafeacb9
Author: Mark Wielaard <m...@klomp.org>
Date: Wed Feb 16 22:56:31 2022 +0100
Warn for execve syscall with argv or argv[0] being NULL.
For execve valgrind would silently fail when argv was NULL or
unadressable. Make sure that this produces a warning under memcheck.
The linux kernel accepts argv[0] being NULL, but most other kernels
don't since posix says it should be non-NULL and it causes argc to
be zero which is unexpected and might cause security issues.
This adjusts some testcases so they don't rely on execve succeeding
when argv is NULL and expect warnings about argv or argv[0] being
NULL or unaddressable.
https://bugs.kde.org/show_bug.cgi?id=450437
Paul, could you push the needed .exp file changes for freebsd?
--
You are receiving this mail because:
You are watching all bug changes.
