software-center crashed with SIGSEGV in __cxa_allocate_exception()

Bug #733084 reported by Jglz
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: software-center

i was searching for flash and then just crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: software-center 3.1.23.1
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
Architecture: amd64
Date: Thu Mar 10 23:36:14 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd126806244 <__cxa_allocate_exception+36>: addl $0x1,0x8(%rax)
 PC (0x7fd126806244) ok
 source "$0x1" ok
 destination "0x8(%rax)" (0x00000018) 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
 FlintTable::set_overwritten() const () from /usr/lib/libxapian.so.22
 FlintTable::block_to_cursor(Cursor_*, int, unsigned int) const () from /usr/lib/libxapian.so.22
 FlintTable::find(Cursor_*) const () from /usr/lib/libxapian.so.22
 FlintCursor::find_entry(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /usr/lib/libxapian.so.22
Title: software-center crashed with SIGSEGV in __cxa_allocate_exception()
UpgradeStatus: Upgraded to natty on 2011-03-10 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jglz (joshshanga) wrote :
Revision history for this message
Anthony Hook (anthonyhook) wrote :

I wasn't able to get software-center running at all, and it crashed (core dumped) when trying to start it from a terminal.

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.