>This is the report: >== 511 tests, 474 stderr failures, 1 stdout failure, 0 post failures == > >The test fails for stderr but if I execute a test (es: memcheck/tests$ >./addressable) it pass.
To run one test, you must do something like: perl tests/vg_regtest memcheck/tests/addressable (the test is not the executable itself, but rather running this executable under valgrind, and compare the output with expected output). If the test still fails, examine in the memcheck/tests directory the files addressable* Some files will give the expected stdout and stderr output, and some files will give what has really be produced. See README_DEVELOPPERS for more information (this is a very valuable source of information :). Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
