Bug 729483

Summary: [abrt] codeblocks-10.05-4.fc14: malloc_consolidate: Process /usr/bin/codeblocks was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: kupon.bg
Component: codeblocksAssignee: Dan Horák <dan>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: alexcvc.soft, dan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:06fc6aac30e17812e483298c9474fca1940c8bbd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 13:33:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description kupon.bg 2011-08-09 21:04:27 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 36478 bytes
cmdline: codeblocks
component: codeblocks
Attached file: coredump, 92729344 bytes
crash_function: malloc_consolidate
executable: /usr/bin/codeblocks
kernel: 2.6.35.13-92.fc14.x86_64
package: codeblocks-10.05-4.fc14
rating: 4
reason: Process /usr/bin/codeblocks was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1312923230
uid: 500

How to reproduce
-----
1. Close Code::Blocks
2.
3.
Comment 1 kupon.bg 2011-08-09 21:04:30 UTC 
Created attachment 517488 [details]
File: backtrace
Comment 2 Alexander Sacharov 2011-08-25 07:10:01 UTC 
Package: codeblocks-10.05-4.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Crush after exit from CodeBlock 10 under F14 on Intel.x48_64
Comment 3 abrt-bot 2012-03-30 13:33:01 UTC 
Backtrace analysis found this bug to be similar to bug #688534, closing as duplicate.

Bugs which were found to be similar to this bug: bug #637488, bug #688534

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 688534 ***