Bug 591932 - [abrt] crash in anjuta-1:2.30.0.0-2.fc13: lookup_iface_entry_I: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in anjuta-1:2.30.0.0-2.fc13: lookup_iface_entry_I: Process /usr/...
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:3e7e8a4fa5a80065c678b92624f...
: 598167 605541 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-13 14:03 UTC by Insang Ryu
Modified: 2010-12-25 14:46 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-25 14:46:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (41.02 KB, text/plain)
2010-05-13 14:03 UTC, Insang Ryu 		no flags Details
View All

Description Insang Ryu 2010-05-13 14:03:51 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: anjuta
comment: I did nothing special. It seems that symbol database causes stability problem sometime.
component: anjuta
crash_function: lookup_iface_entry_I
executable: /usr/bin/anjuta
global_uuid: 3e7e8a4fa5a80065c678b92624f13f49193c861c
kernel: 2.6.33.3-85.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. just editing a file
2.
3.
Comment 1 Insang Ryu 2010-05-13 14:03:53 UTC 
Created attachment 413768 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:50:06 UTC 
*** Bug 598167 has been marked as a duplicate of this bug. ***
Comment 3 Karel Klíč 2010-11-09 16:50:11 UTC 
*** Bug 605541 has been marked as a duplicate of this bug. ***
Comment 4 Johannes Schmid 2010-12-09 09:29:20 UTC 
This has been fixed upstream in 2.32.x!
Comment 5 Johannes Schmid 2010-12-25 14:46:34 UTC 
Sorry, cannot find the bug number of the duplicate bug right now but this one is fixed in the package in f14.

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