I guess in lieu of a better question:

Does anybody actually use address-sanitizers or valgrind or heaptrack and 
eradicates potential memory leaks to the point that _nothing_ shows up while 
they run?

The repeated attempts I've made at using these tools always lead me to areas 
where I never understood what the supposed solution is. Like a memory leak 
reported by heaptrack from `readLine`. That one just makes me assume that 
heaptrack is faulty because I trust the output is getting accurately collected.

I'm developing similar vibes for address sanitizers that they contain a decent 
chunk of "false positives".

Reply via email to