Thanks Tom, I was not sure that was feasible. What is the easiest/standard way in which I can get the source code line of the possible leak? Is it compiling my code against tesseract's source code?
Or should I compile tesseract in debug mode and then use that library? Thanks. On 12/08/2014 07:24 PM, Tom Hughes wrote: > On 08/12/14 19:09, "João M. S. Silva" wrote: > >> Can I provide valgrind with source files so that source code lines of >> libraries compiled without -g are still shown? >> >> For example, I get this memory leak warning: > > [ snipped ] > >> but I can't tell exactly where it comes from. >> >> If I was able to tell valgrind that the source code for tesseract is >> somewhere, it would avoid having to recompile all my code against >> tesseract sources? > > How would that work? Valgrind would still need the debug information in > order to know which addresses in your compiled code map to each line in > the source files... > > Tom > -- João M. S. Silva ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
