Hello, reading from the manual I see that atomic instructions (like lock inc, etc. on x86) are not supported by valgrind in the sense of being emulated in a correct way.
What is the technical reason for this? Are there any plans to correctly handle these instructions? What is the technical difference between handling these and handling pthread's mutexes? Can't valgrind put something like fake mutexes 'around' these atomic variables whenever such an operation is used? Thanks for some insights here, regards! Joerg ------------------------------------------------------------------------------ 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
