[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.

2022-04-07 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=450437 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.

2022-04-06 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=450437 --- Comment #9 from Paul Floyd --- Done -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.

2022-04-06 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=450437 --- Comment #8 from Mark Wielaard --- commit 8eb547054a051a00742b1b9e1b381015fafeacb9 Author: Mark Wielaard 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 fai

[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.

2022-04-03 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=450437 --- Comment #7 from Paul Floyd --- Just scalar and fexecve, the other fexecve tests were OK. The diffs look reasonable (just extra errors for argv/argv[0] like on Linux) -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.

2022-04-03 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=450437 --- Comment #6 from Mark Wielaard --- So do I assume correctly that the generic none/tests/execve, memcheck/tests/execve1 and memchck/tests/execve2 tests PASS with this patch on freebsd, but that the freebsd specific memcheck/tests/freebsd/scalar.vgtest

[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.

2022-04-03 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=450437 --- Comment #5 from Paul Floyd --- Was too quick with the EXTRA_DISTs, they are the patch cruft not the real files There will probably be at least one more .exp (x86 scalar) -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.

2022-04-03 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=450437 --- Comment #4 from Paul Floyd --- Minor thing, missing EXTRA_DISTs memcheck/tests/linux/Makefile.am:1: error: sys-execveat.stderr.exp.orig is missing in EXTRA_DIST memcheck/tests/arm64-linux/Makefile.am:1: error: scalar.stderr.exp.orig is missing in E

[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.

2022-04-03 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=450437 --- Comment #3 from Paul Floyd --- I'll test later today. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.

2022-04-02 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=450437 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.

2022-03-29 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=450437 --- Comment #1 from Paul Floyd --- FreeBSD doesn't allow a zero argc (which is what you get with a NULL argv). This was only enforced relatively recently https://reviews.freebsd.org/R10:773fa8cd136a5775241c3e3a70f1997633ebeedf FreeBSD kernel testcase

[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.

2022-03-29 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=450437 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail