On Fri, 24 Jul 2009, Julian Seward wrote: > >> anyone change it between comparing it to A and setting it to B). Because >> of the way Valgrind works (simulating instructions), the atomic >> instructions get broken up into separate loads/stores, meaning that >> they're no longer atomic (i.e. it's possible for someone to change the >> location in question after it was compared to register A, but before it >> was set to register B). > > That's fixed now, in the trunk (not 3.4.x). If you put in atomic > instructions then you should get out (something equivalent to) > atomic instructions. So V should now play nice with other processes > communicating via shared memory.
Cool, that's good to know :) Is there a place I can read up on how this works? Patrick ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
