10-27-2012, 05:57 PM
I've fixed the two things valgrind has been complaining about in both logs in rev 1013.
I think right now more valgrinding won't bring much useful info, what we need most is find that stupid crash, and it seems valgrind won't help us there.
Maybe the crashdump isn't created because valgrind is taking over. Try running the server without valgrind and make it crash (make sure ulimit -c stayed unlimited in the meantime; it should, unless you restarted the comp)
Oh, by the way, with the speed - welcome to our (developers') world
That slowness is what you get for having a debug build instead of a release build and having a tight memory watcher.
I think right now more valgrinding won't bring much useful info, what we need most is find that stupid crash, and it seems valgrind won't help us there.
Maybe the crashdump isn't created because valgrind is taking over. Try running the server without valgrind and make it crash (make sure ulimit -c stayed unlimited in the meantime; it should, unless you restarted the comp)
Oh, by the way, with the speed - welcome to our (developers') world
That slowness is what you get for having a debug build instead of a release build and having a tight memory watcher.