abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: glob2 component: glob2 executable: /usr/bin/glob2 global_uuid: 66fcc0448482553688a42c0b2616d5a775f67e4f kernel: 2.6.32.12-115.fc12.x86_64 package: glob2-0.9.4.4-1.fc12 rating: 4 reason: Process /usr/bin/glob2 was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine) How to reproduce ----- 1. start program and go to tutorial 2. keep on tutorial and it will crash on "flag and combat" (i thiink this is the name) 3.
Created attachment 421055 [details] File: backtrace
Additional info is needed to file the bug upstream: * Any messages the program printed on the command-line before crashing. * The contents of the "logs" subfolder in your personal "glob2" folder. For Mac and Linux users, this will be "~/.glob2/" * The contents of the "Autosave.game" file in the "games" folder inside your personal "glob2" folder, if the crash was during a game. * If your bug involves a crash during a multiplayer game, you need to provide this information from everyone that was playing the game.
*** Bug 610993 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > Additional info is needed to file the bug upstream: > > * Any messages the program printed on the command-line before crashing. > * The contents of the "logs" subfolder in your personal "glob2" folder. For Mac > and Linux users, this will be "~/.glob2/" > * The contents of the "Autosave.game" file in the "games" folder inside your > personal "glob2" folder, if the crash was during a game. > > * If your bug involves a crash during a multiplayer game, you need to provide > this information from everyone that was playing the game. 1. command-line [christian@merlin ~]$ glob2 glob2: src/Game.cpp:2201: void Game::drawMapGroundBuildings(int, int, int, int, int, int, int, int, int, Uint32, std::set<Building*, std::less<Building*>, std::allocator<Building*> >*): Assertion `building' failed. Aborted (core dumped) 2. the folder "~/.glob2/logs" is empty 3. i will attach to "Autosave.game" 4. Is NOT a multiplayer game.
Created attachment 439738 [details] requested file on previous comment.
*** Bug 625518 has been marked as a duplicate of this bug. ***
Sorry I don't know how to put the back-trace of last core-dump here, soo abrt-daemon created a new bug # 625518 . This new bug I already marked as duplicated of this one.
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.