mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-09 21:28:19 +00:00
854d2ec10e
Problem was that the malloc-replacing tools (memcheck, addrcheck, massif, helgrind) would assert if a too-big malloc was attempted. Now they return 0 to the client. I also cleaned up the code handling heap-block-metadata in Massif and Addrcheck/Memcheck a little. This exposed a nasty bug in VG_(client_alloc)() which wasn't checking if find_map_space() was succeeding before attempting an mmap(). Before I added the check, very big mallocs (eg 2GB) for Addrcheck were overwriting the client space at address 0 and causing crashes. Added a regtest to all the affected skins for this. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2462
10 lines
341 B
Plaintext
10 lines
341 B
Plaintext
|
|
Attempting too-big malloc()...
|
|
Attempting too-big mmap()...
|
|
|
|
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
|
|
malloc/free: in use at exit: 0 bytes in 0 blocks.
|
|
malloc/free: 1 allocs, 0 frees, 2145386496 bytes allocated.
|
|
For a detailed leak analysis, rerun with: --leak-check=yes
|
|
For counts of detected errors, rerun with: -v
|