|
From: Nicholas N. <nj...@cs...> - 2005-03-01 00:34:00
|
On Mon, 28 Feb 2005, Julian Seward wrote: >>>> Recommendation: make --leak-check=yes the default. >>> >>> What about a lightweight leak-check which is always enabled, but only >>> reports a summary of leaked memory, and a CLO which reports the full >>> details of leaked memory? >> >> I don't see much point. People are mostly using --leak-check=yes, let's >> give them what they're (indirectly) asking for. > > I vote for permanently-enabled summary only, with --leak-check=yes > doing the full thing. Would you be able to turn the leak checker off? I think you should still be able to do that. It takes time, if someone doesn't want to use it, they shouldn't have to. > Advantages: > > * it continually reminds users that leak checking is available > > * it means the leak checker is continually exercised, exposing > any bugs sooner These two are true if you have the full output showing too. > * having the full output enabled by default floods people with too > much info they may not want I disagree. I think it's like increasing num-callers -- there's a reasonable concern with flooding the user with too much info, but really the surveys have clearly shown that's what they want. It's better to have too much info than not enough and have to run your program again. Having said that, you're the boss. N |