This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

nightly valgrind?


Hi,

If the test suite is run on a nightly basis on i386, it might be useful to
run the suite twice: once normally, and then once under valgrind. This
may not be practical, depending on how long the suite would take to run
under valgrind. If it is practical, putting a valgrind log up on the
daily snapshots page would be useful.

I started using other runtime analysis tools with unit tests at my real
job and have found this to be invaluable. Getting code coverage wit ha
runtime analysis tool can be a pain and this really helped minimize it.

Valgrind can be found @
http://devel-home.kde.org/~sewardj/ . I believe it's already been used to
find some interesting bugs in gdb, as well as many other programs.


--
http://www.clock.org/~matt


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]