|
From: sukbir s. <sha...@ho...> - 2013-04-01 18:33:29
|
I am very new to valgrind so I have managed to run the programme and output into a log file. It gives me this summary ==4564== LEAK SUMMARY:==4564== definitely lost: 3,550 bytes in 24 blocks==4564== indirectly lost: 4,832 bytes in 13 blocks==4564== possibly lost: 479,613 bytes in 1,806 blocks==4564== still reachable: 3,507,786 bytes in 30,721 blocks==4564== suppressed: 0 bytes in 0 blocks==4564== Reachable blocks (those to which a pointer was found) are not shown.==4564== To see them, rerun with: --leak-check=full --show-reachable=yes==4564== ==4564== For counts of detected and suppressed errors, rerun with: -v==4564== Use --track-origins=yes to see where uninitialised values come from==4564== ERROR SUMMARY: 5929868 errors from 737 contexts (suppressed: 11 from 9). I want to trace now what is the cause of this leaks any idea please? I have with this option valgrind --tool=memcheck --log-file=file-memLog --track-origins=yes --leak-check=yes java myApp1.Thank you. |
|
From: Dan K. <da...@ke...> - 2013-04-01 18:43:42
|
On Mon, Apr 1, 2013 at 11:33 AM, sukbir singh <sha...@ho...> wrote: > I want to trace now what is the cause of this leaks any idea please? I have > with this option valgrind --tool=memcheck --log-file=file-memLog > --track-origins=yes --leak-check=yes java myApp1. I think Valgrind isn't meant for use with java in general... Maybe you want http://stackoverflow.com/questions/40119/how-to-find-a-java-memory-leak ? |
|
From: Eliot M. <mo...@cs...> - 2013-04-01 19:18:17
|
On 4/1/2013 2:43 PM, Dan Kegel wrote: > On Mon, Apr 1, 2013 at 11:33 AM, sukbir singh <sha...@ho...> wrote: >> I want to trace now what is the cause of this leaks any idea please? I have >> with this option valgrind --tool=memcheck --log-file=file-memLog >> --track-origins=yes --leak-check=yes java myApp1. > > I think Valgrind isn't meant for use with java in general... > > Maybe you want http://stackoverflow.com/questions/40119/how-to-find-a-java-memory-leak > ? Agreed. It *might* be relevant for gcj, the GNU compiler for Java, which probably has something more like malloc/free underneath, but even then it might not be appropriate. Regards -- Eliot Moss |