From: Ian S. <ian...@st...> - 2003-04-30 17:29:16
Attachments:
valgrind.supp
|
Funny you should ask, I've just been working on valgrind. No trick - I've added a new patch (for 1.9.4 I think) to the Dart repository. There are some further details in Dart/Web/HTML/Advanced.shtml I have noticed that sometimes Dart does pick up all the output - but I haven't investigated it. It also doesn't display failed tests - which I guess is a problem in the valgrind-handling dart client. I've mostly been working on getting rid of the memory leak false positives. One trick appears to be to declare GLIBCPP_FORCE_NEW as an environment variable before running valgrind. A new valgrind submission with this fix should be on its way to the dashboard sometime soon with about 250 less detected problems! I've included a copy of my extra suppressions file which you are welcome to use. I guess we could share a suppressions file in the VXL repository but it is very fragile so I'm reluctant to let everyone edit it - maybe just email me any additions you find. Currently our testing box only runs valgrind on vcl, v3p, core and mul once a week. I've been keeping track of the load on the box and it looks like we could add one more submission a week, and also test the rest of contrib. The current Valgrind build is currently taking 3.2 hours on a 3.8GHz Xeon - so maybe 4 or 5 hours if we do all of contrib. We can't afford to run it every day, since the same box also runs the documentation builds, our internal continuous builds, and internal valgrind. If you are going to submit to the VXL dashboard a few times a week - we should co-ordinate the days, save ourselves a bit of compute power. I'm planning to submit Monday and Thursdays. Ian. > -----Original Message----- > From: Wheeler, Frederick W (Research) [mailto:wh...@cr...] > Sent: Wednesday, April 30, 2003 5:44 PM > To: Ian Scott > Subject: Valgrind 1.9.5 > > > Ian, > > Is there any trick to upgrading to valgrind 1.9.5 from 1.0.4, with the > respective dart patches? > > Thanks, > Fred > |
From: Andy C. <and...@ki...> - 2003-04-30 17:58:47
|
Hi All, Is there any way for somebody to fix Dart to handle valgrind output correctly? I mean patches to Valgrind are not right approach. Especially since Dart already does regular expression matching, so there should not be to hard to catch valgrind output. Andy On Wed, 2003-04-30 at 13:29, Ian Scott wrote: > Funny you should ask, I've just been working on valgrind. > > No trick - I've added a new patch (for 1.9.4 I think) to the Dart > repository. There are some further details in Dart/Web/HTML/Advanced.shtml > > I have noticed that sometimes Dart does pick up all the output - but I > haven't investigated it. It also doesn't display failed tests - which I > guess is a problem in the valgrind-handling dart client. > > I've mostly been working on getting rid of the memory leak false positives. > One trick appears to be to declare GLIBCPP_FORCE_NEW as an environment > variable before running valgrind. A new valgrind submission with this fix > should be on its way to the dashboard sometime soon with about 250 less > detected problems! > > I've included a copy of my extra suppressions file which you are welcome to > use. I guess we could share a suppressions file in the VXL repository but it > is very fragile so I'm reluctant to let everyone edit it - maybe just email > me any additions you find. > > Currently our testing box only runs valgrind on vcl, v3p, core and mul once > a week. I've been keeping track of the load on the box and it looks like we > could add one more submission a week, and also test the rest of contrib. The > current Valgrind build is currently taking 3.2 hours on a 3.8GHz Xeon - so > maybe 4 or 5 hours if we do all of contrib. We can't afford to run it every > day, since the same box also runs the documentation builds, our internal > continuous builds, and internal valgrind. > > If you are going to submit to the VXL dashboard a few times a week - we > should co-ordinate the days, save ourselves a bit of compute power. I'm > planning to submit Monday and Thursdays. |