abrt 1.0.9 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/bin/codeblocks comment: Code::Blocks crashed for me 12 times in total during random actions, like switching files, moving scrollbar, selecting or pasting, clicking to move caret, pressing F9 to 'compile and run' and such. No special circumstances were involved. component: codeblocks crash_function: _int_malloc executable: /usr/bin/codeblocks global_uuid: 97ca6dc92861b5a0e3b6020495aa882f86d52893 kernel: 2.6.32.11-99.fc12.i686 package: codeblocks-8.02-9.fc12 rating: 4 reason: Process /usr/bin/codeblocks was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1. Use Code::Blocks 2. ?? 3. Profit.
Created attachment 416213 [details] File: backtrace
C::B really should crash that often and during normal work and I haven't seen such behaviour yet. Please can you check whether your OS installation is not damaged and your hardware is OK (run a memory test etc.)? Do you have any large project opened? Can you try to reproduce the problem in the latest nightly build available from http://fedora.danny.cz/danny/ ? It's very close to the upcoming released version.
(In reply to comment #2) > C::B really should crash that often and during normal work and I haven't seen > such behaviour yet. Please can you check whether your OS installation is not > damaged and your hardware is OK (run a memory test etc.)? Do you have any large > project opened? > > Can you try to reproduce the problem in the latest nightly build available from > http://fedora.danny.cz/danny/ ? It's very close to the upcoming released > version. Thanks for the RPM, but I already compiled the svn version (rev 6280). I tried all the actions which seemed to relate to the problems. No crash so far. I don't think it could be caused by OS or harware because I'm not experiencing anything suspicious. And the new installation works without problems. The project I worked on is quite small, some 15 files with roughly 50 - 200 lines each.
Thanks for the update, I will close the issue now as fixed in upstream code.