[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#270147: marked as done (apt: segfault in package removal)

Your message dated Fri, 19 Aug 2011 12:05:22 +0200
with message-id <20110819115258.GA4040@debian.org>
and subject line Re: Bug#81829: "Segmentation faulty tree" (#270147) still present in Lenny, broken /var/cache/apt/*.bin available for download
has caused the Debian Bug report #81829,
regarding apt: segfault in package removal
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
81829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81829
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.5.27
Severity: normal

  # apt-get --purge remove doodle
  Reading Package Lists... Done
  Segmentation faulty Tree... 50%
  # gdb apt-get
  GNU gdb 6.1-debian
  Copyright 2004 Free Software Foundation, Inc.
  GDB is free software, covered by the GNU General Public License, and you
  are
  welcome to change it and/or distribute copies of it under certain
  conditions.
  Type "show copying" to see the conditions.
  There is absolutely no warranty for GDB.  Type "show warranty" for
  details.
  This GDB was configured as "i386-linux"...(no debugging symbols
  found)...Using host libthread_db library "/lib/tls/libthread_db.so.1".
  
  (gdb) r --purge remove doodle
  Starting program: /usr/bin/apt-get --purge remove doodle
  (no debugging symbols found)...(no debugging symbols found)...(no
  debugging symbols found)...(no debugging symbols found)...(no debugging
  symbols found)...(noReading Package Lists... Doneno debugging symbols
  found)...
  Building Dependency Tree... 50%
  Program received signal SIGSEGV, Segmentation fault.
  0x4005f416 in pkgDepCache::CheckDep ()
     from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
  (gdb) bt
  #0  0x4005f416 in pkgDepCache::CheckDep ()
     from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
  #1  0x40060189 in pkgDepCache::DependencyState ()
     from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
  #2  0x400605c7 in pkgDepCache::Update ()
     from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
  #3  0x4005f25f in pkgDepCache::Init ()
     from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
  #4  0x40081014 in pkgCacheFile::Open ()
     from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
  #5  0x0805e277 in std::vector<pkgSrcRecords::Parser::BuildDepRec,
  std::allocator<pkgSrcRecords::Parser::BuildDepRec> >::_M_insert_aux ()
  #6  0x080553cf in ?? ()
  #7  0x40053f3c in CommandLine::DispatchArg ()
     from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
  #8  0x0805d706 in ?? ()
  #9  0x401b27f8 in __libc_start_main () from /lib/tls/libc.so.6
  #10 0x402d4edc in ?? () from /lib/tls/libc.so.6


Other apt bug reports reported success in moving aside
/var/cache/apt/*.bin so I did that and was able to remove the package
without a segfault. I still have the *.bin files if someone needs them.

-- Package-specific info:

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.6-1-686-smp
Locale: LANG=C, LC_CTYPE=C

Versions of packages apt depends on:
ii  libc6                       2.3.2.ds1-16 GNU C Library: Shared libraries an
ii  libgcc1                     1:3.4.1-7    GCC support library
ii  libstdc++5                  1:3.3.4-11   The GNU Standard C++ Library v3

-- no debconf information

--- End Message ---
--- Begin Message --- 
Source: apt
Source-Version: 0.8.16~exp4

apt (0.8.16~exp4) experimental; urgency=low

   [ Julian Andres Klode ]
   * apt-pkg/pkgcache.h:
     - [ABI break] Add pkgCache::Header::CacheFileSize, storing the cache size
   * apt-pkg/pkgcachegen.cc:
     - Write the file size to the cache
   * apt-pkg/pkgcache.cc:
     - Check that cache is at least CacheFileSize bytes large (LP: #16467)

On Thu, Aug 18, 2011 at 04:16:05PM -0500, Jonathan Nieder wrote:
> tags 81829 - moreinfo
> quit
> 
> Axel Beckert wrote:
> 
> > I occasionally ran into this bug on Lenny, can't remember on which
> > platform, but never deterministically.
> >
> > But today I reproducibly ran into this bug with both, apt-get and
> > aptitude. Independent of what I did: aptitude; aptitude -u; aptitude
> > upgrade; apt-get upgrade, I always get the "Segmentation faulty
> > tree... 50%" ("Building dependency tree... 50%^MSegmentation fault").
> >
> > Moving /var/lib/apt/extended_states away didn't help.
> >
> > Couldn't even do an apt-get install gdb for generating a backtrace.
> >
> > Moving away pkgcache.bin and srcpkgcache.bin from /var/cache/apt/
> > finally did help (thanks to waldi for that hint), but copying them
> > back after upgrading two packages didn't reproduce the segfault --
> > they always got recreated.
> 
> Thanks!  No promises about being able to take a look soon, but I've
> downloaded them.
I closed the Launchpad bug in 0.8.16~exp4, but forgot to close that 
one. We still cannot detect invalid caches where data changes, but we
can now detect all truncated caches, and reject them.

I could have included a CRC checksum in the header of the remaining
cache, but our experience so far is that 

 (a) most (all?) of these bugs are the result of truncated cache files
 (b) checksumming the cache on opening is much slower than we want,
     especially on ARM systems (200 ms on abel.d.o, 500 ms on an N900,
     12 ms on my Intel Core i5)

That said, if future shows us cases where there are problems with
correctly-sized caches, we can still add a checksum when we break
ABI again, and enable it by default only on amd64 and other fast
architectures.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Attachment: pgpM7_37S5pR5.pgp
Description: PGP signature


--- End Message ---
Reply to: