r8624: removed valgrind comment on tdb that no longer applies
authorAndrew Tridgell <tridge@samba.org>
Wed, 20 Jul 2005 00:09:23 +0000 (00:09 +0000)
committerGerald (Jerry) Carter <jerry@samba.org>
Wed, 10 Oct 2007 18:29:45 +0000 (13:29 -0500)
(This used to be commit 8f222c8c7a750c739d3288da0b1edb1efc3b1ffc)

source4/lib/tdb/common/tdb.c

index 44533aad2712f267f85c559b982b998cd9943346..4c2d9a1addbf83a17f74ebef0b53981b5b6a839c 100644 (file)
 */
 
 
-/* NOTE: If you use tdbs under valgrind, and in particular if you run
- * tdbtorture, you may get spurious "uninitialized value" warnings.  I
- * think this is because valgrind doesn't understand that the mmap'd
- * area may be written to by other processes.  Memory can, from the
- * point of view of the grinded process, spontaneously become
- * initialized.
- *
- * I can think of a few solutions.  [mbp 20030311]
- *
- * 1 - Write suppressions for Valgrind so that it doesn't complain
- * about this.  Probably the most reasonable but people need to
- * remember to use them.
- *
- * 2 - Use IO not mmap when running under valgrind.  Not so nice.
- *
- * 3 - Use the special valgrind macros to mark memory as valid at the
- * right time.  Probably too hard -- the process just doesn't know.
- */ 
-
 #ifndef _SAMBA_BUILD_
 #if HAVE_CONFIG_H
 #include <config.h>