Description of problem: I was "experimenting" with the game, tried laying down loads of mines, then seeing what would happen if I triggered all of them at once. Not really a good idea, I know! From what I see, some sort of buffer is being overloaded to the point that it causes the game to crash. I may quite possibly be wrong on that though, let me know what you think. Version-Release number of selected component: machineball-1.0-14.fc18 Additional info: backtrace_rating: 4 cmdline: machineball crash_function: init executable: /usr/bin/machineball kernel: 3.8.11-200.fc18.x86_64 uid: 1000 ureports_counter: 1 var_log_messages: May 10 20:09:57 Herschel-HP-RedFox abrt[4589]: Saved core dump of pid 4526 (/usr/bin/machineball) to /var/tmp/abrt/ccpp-2013-05-10-20:09:57-4526 (48123904 bytes) Truncated backtrace: Thread no. 1 (3 frames) #0 init at explosion.cpp:22 #1 ExplosionList::addExplosion at explosion.cpp:49 #2 startGame at game.cpp:461
Created attachment 746448 [details] File: backtrace
Created attachment 746449 [details] File: cgroup
Created attachment 746450 [details] File: core_backtrace
Created attachment 746451 [details] File: dso_list
Created attachment 746452 [details] File: environ
Created attachment 746453 [details] File: limits
Created attachment 746454 [details] File: maps
Created attachment 746455 [details] File: open_fds
Created attachment 746456 [details] File: proc_pid_status
Created attachment 746457 [details] File: xsession_errors
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.