Control: tag -1 pending On Tue, Jul 29, 2014 at 09:01:00PM +0200, Jakub Wilk wrote: > * Michael Vogt <[email protected]>, 2014-07-29, 18:05: > >I wasn't able to reproduce this crash. Could you please try to get a gdb > >backtrace > > Here it goes: > > (gdb) bt > #0 0x00007ffff7785d6e in pkgDepCache::PkgBegin (this=0x0) at > ../build/include/apt-pkg/depcache.h:355 > #1 0x00007ffff779c19b in DoUpdate (CmdL=...) at > /build/apt-S02Gn6/apt-1.0.6/apt-private/private-update.cc:83 > #2 0x00007ffff7b7743e in CommandLine::DispatchArg (this=0x7fffffffeab0, > Map=0x7fffffffead0, NoMatch=true) at > /build/apt-S02Gn6/apt-1.0.6/apt-pkg/contrib/cmndline.cc:380 > #3 0x0000000000401e05 in main (argc=4, argv=0x7fffffffeca8) at > /build/apt-S02Gn6/apt-1.0.6/cmdline/apt.cc:154 >
Thanks for the backtrace. It seems that the DepCache is NULL, so this points to an error in an Open() call, which we did not check. I added a check to debian/experimental in http://anonscm.debian.org/cgit/apt/apt.git/commit/?h=debian/experimental&id=7a139fa8bf2c18da54b5837c9290ba5b77e9c629 This should fix that bug. /me thinks we're not holding the lock file all the time during update, after the lists were fetched, so a parallel update or another APT command could do evil things in the meantime -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Be friendly, do not top-post, and follow RFC 1855 "Netiquette". - If you don't I might ignore you.
