8 Aug
2013
8 Aug
'13
10:42 p.m.
On 08/08/2013 03:56 AM, Steve Glass wrote:
Ok, so its telling you that there is a bad pointer being passed to free. Things you can do: * Set "ulimit -c unlimited" in the shell before running the program. That way you get a "core" file when the program crashes and can run the debugger on it to find out why. * Run valgrind on the executable. When the program finishes it will produce a summary of all memory errors. Hope that helps. Stevie
Hey, Thanks. So I am running op25 with valgrind. i saw a lot of complaints while op25 started and it is running now. it may take some time, maybe hours or maybe days, for op25 to die with this memory problem. so i should wait for it to die right?