mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 18:13:01 +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
27 lines
430 B
Makefile
27 lines
430 B
Makefile
|
|
SUBDIRS = . unused
|
|
|
|
noinst_SCRIPTS = \
|
|
vg_regtest \
|
|
filter_addresses \
|
|
filter_discards \
|
|
filter_numbers \
|
|
filter_stderr_basic \
|
|
filter_test_paths
|
|
|
|
EXTRA_DIST = $(noinst_SCRIPTS)
|
|
|
|
check_PROGRAMS = \
|
|
cputest \
|
|
toobig-allocs \
|
|
true
|
|
|
|
AM_CFLAGS = $(WERROR) -Winline -Wall -Wshadow -g
|
|
AM_CXXFLAGS = $(AM_CFLAGS)
|
|
|
|
# generic C ones
|
|
cputest_SOURCES = cputest.c
|
|
toobig_allocs_SOURCES = toobig-allocs.c
|
|
true_SOURCES = true.c
|
|
|