update-apt-xapian-index crashed with SIGSEGV in pkgCacheGenerator::pkgCacheGenerator()

[write2mahe]

I dont know

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: apt-xapian-index 0.44ubuntu7
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Wed Sep 5 18:13:02 2012
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --update -q
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_IN
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f945097183b: movaps %xmm1,-0x10(%rdi)
 PC (0x7f945097183b) ok
 source "%xmm1" ok
 destination "-0x10(%rdi)" (0x000042e0) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: apt-xapian-index
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 pkgCacheGenerator::pkgCacheGenerator(DynamicMMap*, OpProgress*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgCacheFile::BuildCaches(OpProgress*, bool) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgCacheFile::Open(OpProgress*, bool) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
Title: update-apt-xapian-index crashed with SIGSEGV in pkgCacheGenerator::pkgCacheGenerator()
UpgradeStatus: Upgraded to quantal on 2012-09-05 (0 days ago)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #913962, 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.