software-center crashed with SIGSEGV in __cxa_allocate_exception()

Bug #732128 reported by Jean-Baptiste Lallement
224
This bug affects 51 people
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: software-center

trying to collect a bt for __cxa_allocate_exception() crash

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: software-center 3.1.23.1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Wed Mar 9 17:56:44 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110221)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
SegvAnalysis:
 Segfault happened at: 0x54be6bd <__cxa_allocate_exception+61>: addl $0x1,0x4(%eax)
 PC (0x054be6bd) ok
 source "$0x1" ok
 destination "0x4(%eax)" (0x0000000c) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: software-center
StacktraceTop:
 __cxa_allocate_exception () from /usr/lib/libstdc++.so.6
 Xapian::Database::Database(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /usr/lib/sse2/libxapian.so.22
 _wrap_new_Database__SWIG_1 (self=0x0, args=0x8d0872c) at ../../../../python/modern/xapian_wrap.cc:25493
 _wrap_new_Database (self=0x0, args=0x8d0872c) at ../../../../python/modern/xapian_wrap.cc:25602
 PyEval_EvalFrameEx ()
Title: software-center crashed with SIGSEGV in __cxa_allocate_exception()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sudo

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
visibility: private → public
Revision history for this message
Gary Lasker (gary-lasker) wrote :

Hi Jean-Baptiste, thanks again for your help in gathering the needed debug data for this crash. We were able to determine that the root cause of this bug is in another package, and this crasher is in fact a duplicate of bug 259219. We're now tracking the fix for this over at bug 259219, so I will mark this one as a dupe of that.

Note also that I've added a temporary workaround for the software-center crash to the description for bug 259219.

Thanks again!

tags: added: mago
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.