|
From: Igmar P. <mai...@pa...> - 2012-11-05 10:08:38
|
Hi, I've written a parser which a pretty large resulting codebase. I've still got a few memory leaks. The good part : I know where it leaks. The bad part : That line is a loop, where it allocates a struct, and parses that on into the parser itself. Debugging is an option, but extremely time consuming. What I really want is that valgrind can tell me what is the start of the leaked block. I can enable malloc debugging, but that gives me way to much output. Any suggestions ? Regards, Igmar |