Hide Forgot
abrt version: 1.1.18 architecture: i686 Attached file: backtrace, 10632 bytes cmdline: /usr/bin/gbx2 -g -f /home/myuser/Documents/Gambas/FirstTry -- comment: I never had this happen with Gambas, and have written a skeleton working application with it. That alone took at least a copule of hours just getting familiar with the IDE, controls, etc. I was trying to figure out a problem with a ListView, and added it as a watch. I went to add another watch (or tried to replace the ListView, I don't recall now), and all of a sudden it kind of "froze up", so to speak. Shortly thereafter, I got a message saying that there was no response, and I could wait or just force it to shut down. First, I tried waiting, and played around with some other things for a while. After probably about 5 min., I checked it again. Still no response, so I tried to close it manually and got the close down box again and forced quit. That's about all I can remember about it. component: gambas2 Attached file: coredump, 2928640 bytes crash_function: DEBUG_main executable: /usr/bin/gbx2 kernel: 2.6.35.13-91.fc14.i686 package: gambas2-runtime-2.23.0-1.fc14 rating: 4 reason: Process /usr/bin/gbx2 was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1305912675 uid: 503 How to reproduce ----- 1. Programming with Gambas2 2. Added watch, program froze 3.
Created attachment 500110 [details] File: backtrace
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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