I'm sorry to say so, but the big-ass error log wasn't too useful. When the server crashed, it (of course) "leaked" a lot of memory, so the error is mostly about this leaked memory.
One piece of interesting information, though - the program crashed without valgrind detecting any invalid pointer operations. So there's still something else lurking in the shadows.
Well, keep valgrinding it (update first, so that you have the fixes), something useful is bound to fall out of this
What might help, too: enable core dumps:
http://stackoverflow.com/questions/29193...-c-program
Basically, just run "ulimit -c unlimited" before launching MCServer / valgrind.
Then if the server crashes, hopefully it will create a core dump file, which could be used for post-mortem analysis. I'll need that core dump file and the executable.
Also, I've found out that -ggdb doesn't imply -g, so both flags should probably be present in the makefile.
One piece of interesting information, though - the program crashed without valgrind detecting any invalid pointer operations. So there's still something else lurking in the shadows.
Well, keep valgrinding it (update first, so that you have the fixes), something useful is bound to fall out of this
What might help, too: enable core dumps:
http://stackoverflow.com/questions/29193...-c-program
Basically, just run "ulimit -c unlimited" before launching MCServer / valgrind.
Then if the server crashes, hopefully it will create a core dump file, which could be used for post-mortem analysis. I'll need that core dump file and the executable.
Also, I've found out that -ggdb doesn't imply -g, so both flags should probably be present in the makefile.