I am seeing different results from running an executable on its own vs with valgrind. The culprit is a simple C++ function that returns the square of the double passed to it (the double value is exactly the same (upto precision 20 at least); the square's 16th significant digit differs). The function happens to be inline. Is it a bug that valgrind changes the output of an executable? Is there an option etc to not make this happen? Because of the different results, I'm unable to use valgrind to track the real problem in the code.
I tried adding the same numbers and function to a standalone program but that works fine. All code was built with -m32 -O2 and no other flags. gcc is 4.1, rhel 5; valgrind is 3.3.1 built on both amd64-linux and x86-linux. Thank you. saurabh _________________________________________________________________ Explore the seven wonders of the world http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
