mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 10:05:29 +00:00
8eb547054a
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
11 lines
344 B
Plaintext
11 lines
344 B
Plaintext
Syscall param execve(filename) points to unaddressable byte(s)
|
|
...
|
|
by 0x........: main (execve2.c:9)
|
|
Address 0x........ is not stack'd, malloc'd or (recently) free'd
|
|
|
|
Syscall param execve(argv) points to unaddressable byte(s)
|
|
...
|
|
by 0x........: main (execve2.c:9)
|
|
Address 0x........ is not stack'd, malloc'd or (recently) free'd
|
|
|