]> git.ipfire.org Git - thirdparty/valgrind.git/commit
Change VG_(nuke_all_threads) to disassociate the the stacks of the threads
authorTom Hughes <tom@compton.nu>
Wed, 17 Nov 2004 00:02:04 +0000 (00:02 +0000)
committerTom Hughes <tom@compton.nu>
Wed, 17 Nov 2004 00:02:04 +0000 (00:02 +0000)
commit7c733ecff6373624103577cd883ac0776262d5fb
treebd0bf344a6db1a847c0a4dd6dd523a5d76ca074c
parent8803e1f671f6a87f8fbf6fc60b0e6446ce2ff499
Change VG_(nuke_all_threads) to disassociate the the stacks of the threads
being killed from the threads rather than marking them as inaccessible.

This should fix the problem with the environment (and other data from the
stacks of other threads) causing warnings after a fork. I believe that
VG_(nuke_all_threads) is only called in places where this is the behaviour
that we want or where it doesn't matter because we're about to exit anyway.

MERGE TO STABLE

git-svn-id: svn://svn.valgrind.org/valgrind/branches/VALGRIND_2_2_0_BRANCH@3033
coregrind/vg_scheduler.c