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 04ab67d112a3d8979cad9d2a78e2aa938174413d..569240923a2dc9f08747e823e16f58ec49f010bb 100644 (file)
--- 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