Bug 598500 - [abrt] crash in anjuta-1: raise: Process /usr/bin/anjuta was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in anjuta-1: raise: Process /usr/bin/anjuta was ...
Status: CLOSED DUPLICATE of bug 547030
Alias: None
Product: Fedora
Classification: Fedora
Component: anjuta
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Debarshi Ray
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:4ede4f0102d87a7ccf421c55735...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-01 14:09 UTC by Gregor Neumeyer
Modified: 2010-06-22 09:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-06-22 09:05:51 UTC

Attachments (Terms of Use)
File: backtrace (16.68 KB, text/plain)
2010-06-01 14:09 UTC, Gregor Neumeyer
no flags Details

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 ***

Note You need to log in before you can comment on or make changes to this bug.