On Wed, Apr 10, 2019 at 02:34:10PM +0800, Qu Wenruo wrote: > As we have memleak.py in bcc tools, and it provides better info > including the calling stack, I'm wondering if we should replace current > eb leakage check with bcc based one.
The built-in checks have the advantage that they're built in. So no additional tools or frameworks are needed, either provided by distro or downloaded and built. So for some low-level and crude sanity checks we still want something that ships with the code and can be run as part of normal development & testing loop. Providing additional enhanced output is of course welcome, that's useful when one is actually looking for a specific problem or gathering traces for analysis. So I think we want both, ie. no 'replace'.
