ftmemsim-valgrind/memcheck/tests/execve.stderr.exp
Nicholas Nethercote 6a0aeb3716 Changed error message from:
Address 0x%x is not stack'd, malloc'd or free'd

to

  Address 0x%x is not stack'd, malloc'd or (recently) free'd

This makes things clearer in some circumstances, particularly when bogusly
accessing heap memory that has been freed, but Memcheck is no longer tracking.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2358
2004-04-13 08:36:35 +00:00

15 lines
669 B
Plaintext

Syscall param execve(filename) contains uninitialised or unaddressable byte(s)
at 0x........: execve (in /...libc...)
by 0x........: main (execve.c:8)
Address 0x........ is not stack'd, malloc'd or (recently) free'd
Syscall param execve(argv[i]) contains uninitialised or unaddressable byte(s)
at 0x........: execve (in /...libc...)
by 0x........: main (execve.c:8)
Address 0x........ is not stack'd, malloc'd or (recently) free'd
Syscall param execve(envp[i]) contains uninitialised or unaddressable byte(s)
at 0x........: execve (in /...libc...)
by 0x........: main (execve.c:8)
Address 0x........ is not stack'd, malloc'd or (recently) free'd