On 06/24/2020 06:06 PM, Markus Elfring wrote:
Were any known software analysis tools involved for the detection of
questionable source code places?
kmemleak can detect memory leak,
but I do not know how to detect other kind of leaks.
How do you think about to extend source code analysis tools accordingly?
I have no good idea,
maybe some simple match check tools can do this.
I think consciously release resource in the error path can avoid leaks.
Is it often too easy to overlook relevant function calls?
Yes, I think code review can avoid this issue in some certain degree.
Regards,
Markus
