Bug 598500

Summary: [abrt] crash in anjuta-1: raise: Process /usr/bin/anjuta was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Gregor Neumeyer <levant326>
Component: anjutaAssignee: Debarshi Ray <debarshir>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: debarshir, mschmidt, rpandit
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:4ede4f0102d87a7ccf421c5573519feccd2df793
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-22 09:05:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: backtrace none

Description Gregor Neumeyer 2010-06-01 14:09:06 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: anjuta
component: anjuta
crash_function: raise
executable: /usr/bin/anjuta
global_uuid: 4ede4f0102d87a7ccf421c5573519feccd2df793
package: anjuta-1:
rating: 4
reason: Process /usr/bin/anjuta was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1.This crash always happens as soon as I Create a new sourcefile, regardless what programminglanguage I choose.

Comment 1 Gregor Neumeyer 2010-06-01 14:09:10 UTC
Created attachment 418650 [details]
File: backtrace

Comment 2 Gregor Neumeyer 2010-06-01 14:28:57 UTC
Sorry, but I have to correct myself. This crash happens with c++ source-files. But I have tried it with python and got a new crash-warning in abrt.
Its id is 598503. Maybe this will help a little to find the bug. I could send a crashreport for every available language if you want.

Comment 3 Gregor Neumeyer 2010-06-01 14:38:25 UTC
(In reply to comment #2)
Additional correction! Include c source-files and c/c++ haeder-files

Comment 4 Michal Schmidt 2010-06-22 09:05:51 UTC

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