Jump to content

  • Log In with Google      Sign In   
  • Create Account

#ActualKarsten_

Posted 31 December 2012 - 10:34 AM

Since it crashes over time, it does indeed sound like a slow memory leak.

My suggestion is to compile everything with '-g' (in GCC) to add debugging symbols.

Then run it in "valgrind --tool=memcheck" (Which you should really do before the output leaves the development machine anyway).

This should then tell you all allocations that are not subsequently deallocated so you should be able to pinpoint the issue pretty easily.

#2Karsten_

Posted 31 December 2012 - 10:34 AM

It crashes over time so it sounds like a slow memory leak.

My suggestion is to compile everything with '-g' (in GCC) to add debugging symbols.

Then run it in "valgrind --tool=memcheck" (Which you should really do before the output leaves the development machine anyway).

This should then tell you all allocations that are not subsequently deallocated so you should be able to pinpoint the issue pretty easily.

#1Karsten_

Posted 31 December 2012 - 10:31 AM

It crashes over time so it sounds like a slow memory leak.

 

My suggestion is to compile everything with '-g' (in GCC) to add debugging symbols.

 

Then run it in "valgrind --tool=memcheck" (Which you should really do before the output leaves the development machine anyway).


PARTNERS