mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-04 02:18:37 +00:00
5ab9dd81d6
- 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
20 lines
727 B
Plaintext
20 lines
727 B
Plaintext
|
|
calling sigaltstack, stack base is 0x........
|
|
setting sigaction
|
|
Syscall param sigaction(act) contains uninitialised or unaddressable byte(s)
|
|
at 0x........: __libc_sigaction (...libc...)
|
|
by 0x........: main (sigaltstack.c:27)
|
|
by 0x........: __libc_start_main (...libc...)
|
|
by 0x........: (within /.../tests/sigaltstack)
|
|
Address 0x........ is on thread 1's stack
|
|
res = 0
|
|
raising the signal
|
|
caught signal, local var is on 0x........
|
|
done
|
|
|
|
ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
|
|
malloc/free: in use at exit: 8192 bytes in 1 blocks.
|
|
malloc/free: 1 allocs, 0 frees, 8192 bytes allocated.
|
|
For a detailed leak analysis, rerun with: --leak-check=yes
|
|
For counts of detected errors, rerun with: -v
|