>> 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 think consciously release resource in the error path can avoid leaks. Is it often too easy to overlook relevant function calls? Regards, Markus
