On Tue, Feb 17, 2009 at 11:16 PM, Nicholas Nethercote <[email protected]> wrote: > However, Valgrind serialises multi-threaded execution anyway, so I'm > not sure if losing the atomicity is a problem.
IMHO losing atomicity is definitely a problem in the following case (there might be more examples): a process running under Valgrind on a system with multiple cores or CPU's is updating a location in memory through atomic instructions, where that memory is shared with another process. This issue has been discussed before on the valgrind-devel mailing list. In that discussion Julian stated that he has already been considering to implement proper support for atomic instructions in the VEX library. See also: http://thread.gmane.org/gmane.comp.debugging.valgrind.devel/5471. Bart. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
