Bug 594639

Summary: [abrt] crash in codeblocks-8.02-9.fc12: raise: Process /usr/bin/codeblocks was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: baddaypc
Component: codeblocksAssignee: Dan Horák <dan>
Status: CLOSED DEFERRED QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:11e8ac85a737d6652287a45916541014a7afffe2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-13 08:21:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
File: backtrace none

Description baddaypc 2010-05-21 08:28:40 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: codeblocks
component: codeblocks
crash_function: raise
executable: /usr/bin/codeblocks
global_uuid: 11e8ac85a737d6652287a45916541014a7afffe2
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.Workplace file is open in two instances of Code::Blocks
2. Renamed a file in a project
3. Close the project in the other instance

Comment 1 baddaypc 2010-05-21 08:28:48 UTC
Created attachment 415604 [details]
File: backtrace

Comment 2 Dan Horák 2010-05-24 11:17:03 UTC
Can you try to reproduce the problem in the latest nightly build available from http://fedora.danny.cz/danny/ ?

Comment 3 Dan Horák 2010-07-13 08:21:27 UTC
Code::Blocks 10.05 was pushed to updates. Please open new bug if this behaviour still exists in the new version.