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

[devil89]

Binary package hint: update-notifier

not update software

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 70baf599762784d135d419848bbcc065
CheckboxSystem: 56fed075c56da05a16c3d1e79441e450
Date: Sun Nov 8 12:04:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/update-notifier/apt_check.py
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: wl
Package: update-notifier-common 0.90
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
 LANGUAGE=it_IT.UTF-8
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x195f28 <_ZN17pkgCacheGenerator10ListParser10NewDependsEN8pkgCache11VerIteratorERKSsS4_jj+456>: imul $0x1c,0x8(%eax),%eax
 PC (0x00195f28) ok
 source "$0x1c" ok
 destination "0x8(%eax)" (0x3338ea0c) 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-14-generic i686
UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare scanner video

[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.