From: Tom Hughes Date: Mon, 18 Jul 2005 09:40:29 +0000 (+0000) Subject: Consider blocks with both SF_MMAP and SF_STACK set as part of the root X-Git-Tag: svn/VALGRIND_3_0_0~162 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1afd856f3eded8e62dad594bee8e9af95b538123;p=thirdparty%2Fvalgrind.git Consider blocks with both SF_MMAP and SF_STACK set as part of the root memory set as any additional stack space allocated by valgrind will have both flags set. This fixes bug #106293. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4156 --- diff --git a/coregrind/m_aspacemgr/aspacemgr.c b/coregrind/m_aspacemgr/aspacemgr.c index 7de7bdbb35..92d67b4b70 100644 --- a/coregrind/m_aspacemgr/aspacemgr.c +++ b/coregrind/m_aspacemgr/aspacemgr.c @@ -1185,7 +1185,7 @@ void VG_(find_root_memory)(void (*add_rootrange)(Addr a, SizeT sz)) for (i = 0; i < segments_used; i++) { s = &segments[i]; flags = s->flags & (SF_SHARED|SF_MMAP|SF_VALGRIND|SF_CORE|SF_STACK); - if (flags != SF_MMAP && flags != SF_STACK) + if (flags != SF_MMAP && flags != SF_STACK && flags != (SF_MMAP|SF_STACK)) continue; if ((s->prot & (VKI_PROT_READ|VKI_PROT_WRITE)) != (VKI_PROT_READ|VKI_PROT_WRITE))