mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-04 10:21:20 +00:00
- For all except `trivialleak', expected output lines like this:
by 0x........: __libc_start_main@@GLIBC_2.0 (...libc...)
were changed to look like this:
by 0x........: (within /.../tests/supp2)
This change was caused by a change about 3 weeks ago, but we couldn't work
out exactly which one. It does not seem unreasonable, though.
- For `malloc1' and `trivialleak', one of the line numbers changed -- they
are now correct instead of off by one -- thanks to Jeremy F's recent patch
which subtracts one from return addresses (for exactly this reason).
Now they all pass again except `tronical', as expected.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1328
18 lines
713 B
Plaintext
18 lines
713 B
Plaintext
|
|
Invalid read of size 4
|
|
at 0x........: addemup (inline.c:10)
|
|
by 0x........: main (inline.c:18)
|
|
by 0x........: __libc_start_main (...libc...)
|
|
by 0x........: (within /.../tests/inline)
|
|
Address 0x........ is 0 bytes after a block of size 40 alloc'd
|
|
at 0x........: calloc (vg_clientfuncs.c:...)
|
|
by 0x........: main (inline.c:17)
|
|
by 0x........: __libc_start_main (...libc...)
|
|
by 0x........: (within /.../tests/inline)
|
|
|
|
ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
|
|
malloc/free: in use at exit: 40 bytes in 1 blocks.
|
|
malloc/free: 1 allocs, 0 frees, 40 bytes allocated.
|
|
For a detailed leak analysis, rerun with: --leak-check=yes
|
|
For counts of detected errors, rerun with: -v
|