software-center crashed with SIGSEGV in __cxa_allocate_exception()

[Matthew Paul Thomas]

Binary package hint: software-center

Apport says:

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 14:51:43 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x2e3a6bd <__cxa_allocate_exception+61>: addl $0x1,0x4(%eax)
 PC (0x02e3a6bd) 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
 ?? () from /usr/lib/python2.7/dist-packages/xapian/_xapian.so
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
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

[Apport retracing service (apport)]

StacktraceTop:
 __cxa_allocate_exception () from /usr/lib/libstdc++.so.6
 Xapian::Database::Database (this=0xa807348, path=...) at ../backends/dbfactory.cc:343
 _wrap_new_Database__SWIG_1 (self=0x0, args=0xa78fc4c) at ../../../../python/modern/xapian_wrap.cc:25493
 _wrap_new_Database (self=0x0, args=0xa78fc4c) at ../../../../python/modern/xapian_wrap.cc:25602
 ext_do_call (f=0xa7ebb8c, throwflag=0) at ../Python/ceval.c:4323

[Gary Lasker (gary-lasker)]

Hey mpt, thanks for the report! We've determined 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 a temporary workaround for the software-center crash has been added to the description for bug 259219.

Thanks again!