mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-08 04:55:52 +00:00
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
15 lines
491 B
Makefile
15 lines
491 B
Makefile
noinst_SCRIPTS = filter_stderr
|
|
|
|
INSN_TESTS=insn_basic insn_fpu insn_cmov insn_mmx insn_mmxext insn_sse insn_sse2
|
|
|
|
EXTRA_DIST = $(noinst_SCRIPTS) \
|
|
badrw.stderr.exp badrw.vgtest \
|
|
fprw.stderr.exp fprw.vgtest \
|
|
insn_basic.vgtest insn_cmov.vgtest insn_mmx.vgtest \
|
|
$(addsuffix .stderr.exp,$(INSN_TESTS)) \
|
|
$(addsuffix .stdout.exp,$(INSN_TESTS)) \
|
|
$(addsuffix .vgtest,$(INSN_TESTS)) \
|
|
overlap.stderr.exp overlap.stdout.exp overlap.vgtest \
|
|
toobig-allocs.stderr.exp toobig-allocs.vgtest
|
|
|