Bug 613468 - [abrt] crash in codeblocks-8.02-9.fc12: raise: Process /usr/bin/codeblocks was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in codeblocks-8.02-9.fc12: raise: Process /usr/bin/codeblocks wa...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: codeblocks
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:02d0558e6294f206e10312ffcc2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-11 21:52 UTC by Andrés Montandon
Modified: 2010-07-13 08:22 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-07-13 08:22:14 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (79.19 KB, text/plain)
2010-07-11 21:52 UTC, Andrés Montandon 		no flags Details
View All

Description Andrés Montandon 2010-07-11 21:52:00 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: codeblocks
component: codeblocks
crash_function: raise
executable: /usr/bin/codeblocks
global_uuid: 02d0558e6294f206e10312ffcc247063a5fea046
kernel: 2.6.32.14-127.fc12.i686.PAE
package: codeblocks-8.02-9.fc12
rating: 4
reason: Process /usr/bin/codeblocks was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Go to the menu "Debug-> Edit watches ..."
2. Add a new watches (I added one called "Text") and press "OK" ...
3. Go back to "Debug-> Edit watches ..." and try to eliminate the watches who did ...
4. There is an error.

(Spanish)
1. Ir al menú "Debug->Edit watches..." 
2. Agregar un nuevo observador (yo agregue uno llamado "Text") y presionar "Aceptar"...
3. Ir nuevamente a "Debug->Edit watches..." y intentar eliminar el observador que creamos...
4. Se produce un error.
Comment 1 Andrés Montandon 2010-07-11 21:52:11 UTC 
Created attachment 431028 [details]
File: backtrace
Comment 2 Dan Horák 2010-07-13 08:22:14 UTC 
Code::Blocks 10.05 was pushed to updates. Please open new bug if this behaviour still exists in the new version.
Note You need to log in before you can comment on or make changes to this bug.