Version-Release number of selected component: megaglest-3.7.1-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/megaglest core_backtrace: crash_function: Glest::Game::Program::loopWorker executable: /usr/bin/megaglest kernel: 3.8.3-203.fc18.i686 uid: 1000 var_log_messages: Mar 20 12:13:55 localhost abrt[6071]: Saved core dump of pid 5925 (/usr/bin/megaglest) to /var/spool/abrt/ccpp-2013-03-20-12:13:51-5925 (220594176 bytes) Truncated backtrace: Thread no. 1 (10 frames) #5 Glest::Game::Program::loopWorker at /usr/src/debug/megaglest-3.7.1/source/glest_game/main/program.cpp:393 #6 Glest::Game::ExceptionHandler::handleRuntimeError at /usr/src/debug/megaglest-3.7.1/source/glest_game/main/main.cpp:445 #7 Glest::Game::handleSIGSEGV at /usr/src/debug/megaglest-3.7.1/source/glest_game/main/main.cpp:4938 #9 __pthread_mutex_lock at pthread_mutex_lock.c:50 #10 SDL_mutexP at src/thread/pthread/SDL_sysmutex.c:108 #11 Shared::Platform::Mutex::p at /usr/src/debug/megaglest-3.7.1/source/shared_lib/sources/platform/sdl/thread.cpp:176 #12 Lock at /usr/src/debug/megaglest-3.7.1/source/shared_lib/include/platform/sdl/thread.h:139 #13 MutexSafeWrapper at /usr/src/debug/megaglest-3.7.1/source/shared_lib/include/platform/sdl/thread.h:112 #14 Shared::PlatformCommon::IRCThread::setCallbackObj at /usr/src/debug/megaglest-3.7.1/source/shared_lib/sources/platform/posix/ircclient.cpp:543 #15 Glest::Game::cleanupProcessObjects at /usr/src/debug/megaglest-3.7.1/source/glest_game/main/main.cpp:170
Created attachment 713436 [details] File: backtrace
Created attachment 713437 [details] File: cgroup
Created attachment 713438 [details] File: dso_list
Created attachment 713439 [details] File: environ
Created attachment 713440 [details] File: limits
Created attachment 713441 [details] File: maps
Created attachment 713442 [details] File: open_fds
Created attachment 713443 [details] File: proc_pid_status
Do you have some easy procedure to reproduce the problem? To help understand the reason of the bad/bogus pointer with "0xd" value. It looks like a dangling pointer to a deleted object was used. #9 __GI___pthread_mutex_lock (mutex=mutex@entry=0xd) at pthread_mutex_lock.c:50 type = <optimized out> id = <optimized out> #10 0x4117f910 in SDL_mutexP (mutex=0xd) at src/thread/pthread/SDL_sysmutex.c:108 retval = 0 #11 0x0861aac0 in Shared::Platform::Mutex::p (this=0xa356be4) at /usr/src/debug/megaglest-3.7.1/source/shared_lib/sources/platform/sdl/thread.cpp:176 __FUNCTION__ = "p" #12 0x08623e6d in Lock (this=0xbf9f0e40) at /usr/src/debug/megaglest-3.7.1/source/shared_lib/include/platform/sdl/thread.h:139
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days