anjuta crashed with SIGSEGV in symbol_db_engine_add_new_files_full()

Bug #440315 reported by Forrest.Zhang
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
anjuta (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: anjuta

anjuta crashed when create a new gtk+ project.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Oct 2 10:04:32 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/anjuta
Package: anjuta 2:2.28.0.0-0ubuntu1
ProcCmdline: anjuta
ProcEnviron:
 LANGUAGE=zh_CN.UTF-8
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x1109728: cmpl $0x40,(%eax)
 PC (0x01109728) ok
 source "$0x40" ok
 destination "(%eax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: anjuta
StacktraceTop:
 ?? () from /usr/lib/anjuta/libanjuta-symbol-db.so
 symbol_db_engine_add_new_files_full ()
 ?? () from /usr/lib/anjuta/libanjuta-symbol-db.so
 ?? () from /usr/lib/anjuta/libanjuta-symbol-db.so
 ?? () from /usr/lib/libanjuta.so.0
Title: anjuta crashed with SIGSEGV in symbol_db_engine_add_new_files_full()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #441463, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.