|
From: Milian W. <ma...@mi...> - 2012-11-05 11:52:55
|
On Monday 05 November 2012 10:48:32 Igmar Palsenberg wrote: > 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. I don't get it - if you know where it leaks you can fix it, no? If you want to get memory adresses of leaked blocks (for whatever reason?), just use memcheck's --leak-check=full, afaik that shows the addresses and size of the leaked objects. bye -- Milian Wolff ma...@mi... http://milianw.de |