On Thu, Sep 12, 2019 at 08:21:38PM -0600, Warner Losh wrote: > When multiple people are doing leak busting, maybe over years, they > eliminate many false positives so you can focus on the real issues w/o a > run time penalty. Especially something in the library that comes up > often... otherwise they get in the way of making progress...
Instead of adding rarely excercised code in the exit path, I would prefer to mark the allocation with something special so the sanitizer knows I intend to never free the result and I am fine with "the leak". It could still report a summary like "10k in 20 objects allocated and intentionaly not freed", so if this goes up dramatically we may still notice. Martin
