[lacks info] 3.6.0.3: Crash (freeze?) during game while hosting on Windows

[victorj]

Code: [Select]

[2012-06-30 00:55:28] Runtime Error information:
======================================================
In [/build/buildd/megaglest-3.6.0.3/source/glest_game/main/main.cpp::handleSIGSEGV Line: 652] Error detected: signal 11:

Stack Trace:
/usr/games/megaglest() [0x5d26b2] address [0x5d26b2] line: 0
/lib/x86_64-linux-gnu/libpthread.so.0:() address [0x7f23199c8cb0] line: 0
/usr/games/megaglest:Shared::PlatformCommon::SimpleTaskThread::~SimpleTaskThread() address [0x83ad6c] line: 0
/usr/games/megaglest:Shared::PlatformCommon::SimpleTaskThread::execute() address [0x83c91b] line: 0
/usr/games/megaglest:Shared::Platform::Thread::beginExecution(void*) address [0x86908f] line: 0
/usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0:() address [0x7f2319be8fd5] line: 0
/usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0:() address [0x7f2319c2c999] line: 0
/lib/x86_64-linux-gnu/libpthread.so.0:() address [0x7f23199c0e9a] line: 0
/lib/x86_64-linux-gnu/libc.so.6:clone() address [0x7f2316c564bd] line: 0


Megaglest version: 3.6.0.3

System: Ubuntu 12.04 Precise Pangolin 64-bits + KDE 4.8

I was playing online on my host when I had crash, and these lines on my error.log I had to Reboot my computer using graphic mode.

[tomreyn]

I think this stack trace does unfortunately not provide enough information to tell what's gone wrong. After all no line numbers are provided, and the code location just says that something went wrong while working on something threaded. I think stack traces are improved in the code which is in subversion, but for 3.6.0.3 it would take the verbose output, and possibly debug logging, too, to tell what went wrong here.

I also assume that most bugs in 3.6.0.3 are now fixed in the code available in the subversion repository, so it's much better to test with a current development build. Since if you find bugs there, then it's much more worth to spend some time on finding out what went wrong, why, and how to fix it because you aren't risking to waste 10 minutes skimming debug log files just to end up with "oh we already fixed this bug three months ago". (That's a situation which can increase developers' motivation to have a new release actually.)

[softcoder]

Is this reproducible?

[victorj]

Is this reproducible?

Yes, but not the same way, I had others crashes, when I clicked the button to start the game on my host server my megaglest closed, and the same lines in error.log.

[softcoder]

You need to post the exact steps you took to make this happen, or ewlse we cannot reproduce it ourselves and thus cannot fix it. Please follow the sticky thread about how to post bugs.