[lacks info] 3.6.0.3 Segfault on headless server

[tomreyn]

There was another segfault on a headless server (summoner) in late february. I don't know what triggered it and how it happened, I only spotted the core file later.

Backtrace:

Code: [Select]

[New Thread 7227]
[New Thread 7231]
[New Thread 7230]
[New Thread 7229]
[New Thread 7228]
[New Thread 7226]
[New Thread 7225]
[New Thread 7224]
[New Thread 7223]
[New Thread 7177]
[New Thread 7174]
[New Thread 7173]
[New Thread 7172]
[New Thread 7171]

warning: Can't read pathname for load map: Input/output error.
Can't read symbols from system-supplied DSO at 0x7fffd4da4000: File truncated
Core was generated by `./megaglest --ini-path=./ --data-path=./ --headless-server-mode=vps,exit'.
Program terminated with signal 6, Aborted.
#0  0x00002b178326cd05 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#0  0x00002b178326cd05 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00002b1783270ab6 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00002b1782b526dd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x00002b1782b50926 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00002b1782b50953 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x00002b1782b50a5e in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x00000000008a99c5 in Glest::Game::FactionThread::execute (this=0x2b179c127760) at /home/softcoder/Code/megaglest/branches/release-3.6.0.3/source/glest_game/type_instances/faction.cpp:359
#7  0x00000000009c3e9f in Shared::Platform::Thread::beginExecution (data=0x1c03) at /home/softcoder/Code/megaglest/branches/release-3.6.0.3/source/shared_lib/sources/platform/sdl/thread.cpp:79
#8  0x00002b17805dba05 in ?? () from /usr/lib/libSDL-1.2.so.0
#9  0x00002b178061e649 in ?? () from /usr/lib/libSDL-1.2.so.0
#10 0x00002b1780866d8c in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#11 0x00002b178331f04d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#12 0x0000000000000000 in ?? ()

The standard output/error is available, too.

[tomreyn]

This stacktrace didn't provide enough information and 3.6.0.3 is old, so I'll close it with [lacks info].