From: Julian Seward Date: Tue, 3 May 2005 17:36:08 +0000 (+0000) Subject: Fix expected output. It could be that having CFI-based tracebacks X-Git-Tag: svn/VALGRIND_3_0_0~712 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=8cc6d78dc7255befecaefee473e5d309b97a9120;p=thirdparty%2Fvalgrind.git 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 --- diff --git a/memcheck/tests/buflen_check.stderr.exp b/memcheck/tests/buflen_check.stderr.exp index 04ab67d112..569240923a 100644 --- a/memcheck/tests/buflen_check.stderr.exp +++ b/memcheck/tests/buflen_check.stderr.exp @@ -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