apt_check.py crashed with SIGSEGV in pkgCacheGenerator::ListParser::NewDepends()

[antdl]

Binary package hint: update-notifier

crash on Virtual box

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Oct 4 22:47:09 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/update-notifier/apt_check.py
InterpreterPath: /usr/bin/python2.6
Package: update-notifier-common 0.88
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0xcc5f28 <_ZN17pkgCacheGenerator10ListParser10NewDependsEN8pkgCache11VerIteratorERKSsS4_jj+456>: imul $0x1c,0x8(%eax),%eax
 PC (0x00cc5f28) ok
 source "$0x1c" ok
 destination "0x8(%eax)" (0xf873fb30) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 pkgCacheGenerator::ListParser::NewDepends(pkgCache::VerIterator, std::string const&, std::string const&, unsigned int, unsigned int) ()
 debListParser::ParseDepends(pkgCache::VerIterator, char const*, unsigned int) () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
 debListParser::NewVersion(pkgCache::VerIterator) ()
 pkgCacheGenerator::MergeList(pkgCacheGenerator::ListParser&, pkgCache::VerIterator*) () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
 debStatusIndex::Merge(pkgCacheGenerator&, OpProgress&) const
Title: apt_check.py crashed with SIGSEGV in pkgCacheGenerator::ListParser::NewDepends()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout dip lpadmin netdev plugdev sambashare

[Apport retracing service (apport)]

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 #440498, 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.