mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-11 22:08:14 +00:00
9d3d254a8b
The VG_(extend_stack) call needs to be properly guarded because the
passed-in address is not necessarily part of an extensible stack
segment. And an extensible stack segment is the only thing that
function should have to deal with.
Previously, the function VG_(am_addr_is_in_extensible_client_stack)
was introduced to guard VG_(extend_stack) but it was not added in all
places it should have been.
Also, extending the client stack during signal delivery (in sigframe-common.c)
was simply calling VG_(extend_stack) hoping it would do the right thing.
But that was not always the case. The new testcase
none/tests/linux/pthread-stack.c exercises this (3.10.1 errors out on it).
Renamed ML_(sf_extend_stack) to ML_(sf_maybe_extend_stack) and add
proper guard logic for VG_(extend_stack).
Testcases none/tests/{amd64|x86}-linux/bug345887.c by Ivo Raisr.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15138
29 lines
660 B
Makefile
29 lines
660 B
Makefile
|
|
include $(top_srcdir)/Makefile.tool-tests.am
|
|
|
|
dist_noinst_SCRIPTS = filter_stderr
|
|
|
|
EXTRA_DIST = \
|
|
blockfault.stderr.exp blockfault.vgtest \
|
|
mremap.stderr.exp mremap.stderr.exp-glibc27 mremap.stdout.exp \
|
|
mremap.vgtest \
|
|
mremap2.stderr.exp mremap2.stdout.exp mremap2.vgtest \
|
|
mremap3.stderr.exp mremap3.stdout.exp mremap3.vgtest \
|
|
pthread-stack.stderr.exp pthread-stack.vgtest \
|
|
stack-overflow.stderr.exp stack-overflow.vgtest
|
|
|
|
check_PROGRAMS = \
|
|
blockfault \
|
|
mremap \
|
|
mremap2 \
|
|
mremap3 \
|
|
pthread-stack \
|
|
stack-overflow
|
|
|
|
|
|
AM_CFLAGS += $(AM_FLAG_M3264_PRI)
|
|
AM_CXXFLAGS += $(AM_FLAG_M3264_PRI)
|
|
|
|
# Special needs
|
|
pthread_stack_LDADD = -lpthread
|