From: Bart Van Assche Date: Sat, 12 Mar 2011 14:26:01 +0000 (+0000) Subject: DRD: Restored --free-is-write support and fixed the bug that was present in the previ... X-Git-Tag: svn/VALGRIND_3_7_0~593 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=84b87cf1e72f77b5b784d9344b877a771af984f8;p=thirdparty%2Fvalgrind.git DRD: Restored --free-is-write support and fixed the bug that was present in the previous implementation. Still needs further testing though. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11636 --- diff --git a/drd/docs/drd-manual.xml b/drd/docs/drd-manual.xml index 21adaa2125..4b0090a4a1 100644 --- a/drd/docs/drd-manual.xml +++ b/drd/docs/drd-manual.xml @@ -361,6 +361,42 @@ behavior of the DRD tool itself: + + + + + + + Whether to report races between accessing memory and freeing + memory. Enabling this option may cause DRD to run slightly + slower. Notes: + + + + Don't enable this option when using custom memory allocators + that use + the VG_USERREQ__MALLOCLIKE_BLOCK + and VG_USERREQ__FREELIKE_BLOCK + because that would result in false positives. + + + + Don't enable this option when using reference-counted + objects because that will result in false positives, even when + that code has been annotated properly with + ANNOTATE_HAPPENS_BEFORE + and ANNOTATE_HAPPENS_AFTER. See + e.g. the output of the following command for an example: + valgrind --tool=drd --free-is-write=yes + drd/tests/annotate_smart_pointer. + + + + + +