From: Richard B. <ri...@ta...> - 2003-05-14 12:50:57
|
On Wed, 2003-05-14 at 11:33, Crispin Flowerday wrote: > Ahh, that explains it. Perhaps the leak-resolution should default to med > or high as the output was extremely confusing (much worse when you have > a large application and valgrind has merged 10 blocks into a single > stacktrace). Wouldn't that result in confusing, or at least excessively repetitive, output when the same leak is happening multiple times when called from different places? How about changing the leak checker to compare the names up to the first name in the stack trace that isn't in part of valgrind? This would exclude the allocation functions quite neatly, which seems desirable. Perhaps there are problems with this that I can't see, though. Incidentally, I was going to try putting a patch for this together, but can't seem to update my checkout of valgrind CVS. In fact, I can't even do the cvs login: $ cvs -d:pserver:ano...@cv...:/cvsroot/valgrind login Logging in to :pserver:ano...@cv...:2401/cvsroot/valgrind CVS password: cvs [login aborted]: connect to cvs.sourceforge.net(66.35.250.207):2401 failed: Connection refused (just pressing return for the password) Is this just me and the lightning storms around here, or is it sourceforge? -- Richard |