abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: supertux component: supertux executable: /usr/bin/supertux kernel: 2.6.31.12-174.2.22.fc12.x86_64 package: supertux-0.3.1-9.fc12 rating: 4 reason: Process /usr/bin/supertux was killed by signal 7 (SIGBUS) release: Fedora release 12 (Constantine)
Created attachment 400586 [details] File: backtrace
It looks like the drawing requests buffer got corrupted. Without steps to reproduce, I don't know where to look for the problem.
How to reproduce ----- 1. Entering level "shocking". Next time it didn't crash. 2. 3.
(In reply to comment #3) > How to reproduce > ----- > 1. Entering level "shocking". Next time it didn't crash. Thanks for the hint! I have seen such a crash before. I did some testing and can reproduce it consistently by doing the following: 1. Play "Under Construction" until Tux lands on the floor of the secret area, then quit the level. 2. Start "Shocking". I bisected and found that it was fixed upstream in r5356. The issue is probably the same as in this upstream bug: http://supertux.lethargik.org/bugs/view.php?id=231 SuperTux 0.3.3 contains the fix.
I poked a little more, and the problem is definitely the one described in the upstream bug. "Shocking" and "Light and Magic" are the only two levels on the standard world map that have non-white ambient light and thus enable the lightmap, which triggers the crash. In the case of "Under Construction", the lightmap requests are coming from pulsing lights added to the lava by Sector::fix_old_tiles.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. Thank you for reporting this bug and we are sorry it could not be fixed.
*** Bug 617183 has been marked as a duplicate of this bug. ***
Note this crash is fixed in supertux-0.3.3 which is available in Fedora 14 and later.