Bug 621096 - [abrt] crash in anjuta-1:2.30.0.0-2.fc13: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in anjuta-1:2.30.0.0-2.fc13: Process /usr/bin/anjuta was killed ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: anjuta
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Debarshi Ray
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b5f53b29cc415e1fdc67b350dd0...
: 626582 627059 639176 639814 641417 653622 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-04 08:56 UTC by blachniom
Modified: 2010-12-13 16:20 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-13 16:09:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (31.84 KB, text/plain)
2010-08-04 08:56 UTC, blachniom
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 630811 0 None None None Never

Description blachniom 2010-08-04 08:56:30 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: anjuta
comment: This does not occur every time. In fact, it was the second time I observed it.
component: anjuta
crash_function: gtk_source_completion_model_iter_last
executable: /usr/bin/anjuta
global_uuid: b5f53b29cc415e1fdc67b350dd0ff9e7d58f048a
kernel: 2.6.33.6-147.2.4.fc13.i686
package: anjuta-1:2.30.0.0-2.fc13
rating: 4
reason: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. try to change one (previously declared) variable name, to another (also previously declared)
2. when the source completion/hint window appears, press escape

Comment 1 blachniom 2010-08-04 08:56:33 UTC
Created attachment 436475 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 13:17:39 UTC
*** Bug 639176 has been marked as a duplicate of this bug. ***

Comment 3 Johannes Schmid 2010-12-09 09:34:54 UTC
This has been fixed upstream in 2.32.x!

Comment 4 Johannes Schmid 2010-12-13 16:09:27 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 5 Johannes Schmid 2010-12-13 16:10:12 UTC
*** Bug 626582 has been marked as a duplicate of this bug. ***

Comment 6 Johannes Schmid 2010-12-13 16:10:49 UTC
*** Bug 627059 has been marked as a duplicate of this bug. ***

Comment 7 Johannes Schmid 2010-12-13 16:13:05 UTC
*** Bug 639814 has been marked as a duplicate of this bug. ***

Comment 8 Johannes Schmid 2010-12-13 16:14:08 UTC
*** Bug 641417 has been marked as a duplicate of this bug. ***

Comment 9 Johannes Schmid 2010-12-13 16:20:15 UTC
*** Bug 653622 has been marked as a duplicate of this bug. ***


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