On 25/03/2012 20:47, Robert Paulson wrote:
Speaking of frequent crashes, does anyone else get this stack trace?
It has been happening for about a year now, and I thought Valve would
fix it, but maybe I am the only one with this problem.
Program terminated with signal 6, Aborted.
0xf779f430 in __kernel_vsyscall ()
0xf779f430 in __kernel_vsyscall ()
0xf74eec4f in raise () from /lib32/libc.so.6
0xf74f2175 in abort () from /lib32/libc.so.6
0xf752621c in ?? () from /lib32/libc.so.6
0xf7530f02 in ?? () from /lib32/libc.so.6
0xf7532897 in ?? () from /lib32/libc.so.6
0xf75347c1 in malloc () from /lib32/libc.so.6
0xf775daa3 in CStdMemAlloc::Alloc(unsigned int) () from bin/libtier0.so
0xf3db4d86 in CUtlVector<CUserCmd, CUtlMemory<CUserCmd, int>
The c library is calling abort() while allocating memory ( malloc()
calls earlier in trace) which suggests it's memory starvation or heap
corruption of some description.
It looks like it's related to processing user commands for bots,
guessing from the symbol names, which might explain why others don't get it.
--
Dan.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
