mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 18:13:01 +00:00
Fix expected output. It could be that having CFI-based tracebacks
made the stack traces in the error messages less crappy. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3606
This commit is contained in:
parent
68dbd9d954
commit
8cc6d78dc7
@ -1,13 +1,11 @@
|
||||
Syscall param socketcall.getsockname(name) points to unaddressable byte(s)
|
||||
at 0x........: getsockname (in /...libc...)
|
||||
by 0x........: __libc_start_main (in /...libc...)
|
||||
by 0x........: ...
|
||||
by 0x........: main (buflen_check.c:18)
|
||||
Address 0x........ is not stack'd, malloc'd or (recently) free'd
|
||||
|
||||
Syscall param socketcall.getsockname(namelen_in) points to unaddressable byte(s)
|
||||
at 0x........: getsockname (in /...libc...)
|
||||
by 0x........: __libc_start_main (in /...libc...)
|
||||
by 0x........: ...
|
||||
by 0x........: main (buflen_check.c:19)
|
||||
Address 0x........ is not stack'd, malloc'd or (recently) free'd
|
||||
getsockname(1) failed
|
||||
getsockname(2) failed
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user