Bug#554387: marked as done (rred segfaults during apt-get update if pkgcache.bin is corrupted)
Your message dated Wed, 23 May 2012 15:32:07 +0200
with message-id <CAAZ6_fCZypnH5Ff3GZ4mu++xHM7Z8mJ0hECoSa5_gPO7iOvWgQ@mail.gmail.com>
and subject line Re: Bug#670401: Bug#673065: rred segfaults during apt-get update
has caused the Debian Bug report #670401,
regarding rred segfaults during apt-get update if pkgcache.bin is corrupted
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.)
--
670401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670401
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: /usr/bin/apt-get: segmentation fault when trying to update
- From: Salvo Tomaselli <tiposchi@tiscali.it>
- Date: Wed, 04 Nov 2009 09:04:49 +0100
- Message-id: <20091104080449.15999.29511.reportbug@localhost>
Package: apt
Version: 0.7.24
Severity: normal
File: /usr/bin/apt-get
# apt-get update
[...] blablabla
Scaricare:15 http://ftp.ch.debian.org unstable/main 2009-11-04-0016.39.pdiff [5001kB]
E: Method rred has died unexpectedly!
E: Il sottoprocesso rred ha ricevuto un segmentation fault.
# dmesg
[...] blablabla
rred[15924]: segfault at bf498fe4 ip b7c5c8af sp bf498fe8 error 6 in libc-2.10.1.so[b7bf5000+141000]
-- Package-specific info:
-- apt-config dump --
APT "";
APT::Architecture "i386";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Acquire "";
APT::Acquire::Translation "environment";
APT::Acquire::Max-Default-Age "";
APT::Acquire::Max-Default-Age::Debian-Security "7";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^linux-image.*";
APT::NeverAutoRemove:: "^linux-restricted-modules.*";
Dir "/";
Dir::State "var/lib/apt/";
Dir::State::lists "lists/";
Dir::State::cdroms "cdroms.list";
Dir::State::userstatus "status.user";
Dir::State::status "/var/lib/dpkg/status";
Dir::Cache "var/cache/apt/";
Dir::Cache::archives "archives/";
Dir::Cache::srcpkgcache "srcpkgcache.bin";
Dir::Cache::pkgcache "pkgcache.bin";
Dir::Etc "etc/apt/";
Dir::Etc::sourcelist "sources.list";
Dir::Etc::sourceparts "sources.list.d";
Dir::Etc::vendorlist "vendors.list";
Dir::Etc::vendorparts "vendors.list.d";
Dir::Etc::main "apt.conf";
Dir::Etc::parts "apt.conf.d";
Dir::Etc::preferences "preferences";
Dir::Etc::preferencesparts "preferences.d";
Dir::Bin "";
Dir::Bin::methods "/usr/lib/apt/methods";
Dir::Bin::dpkg "/usr/bin/dpkg";
Dir::Log "var/log/apt";
Dir::Log::Terminal "term.log";
DPkg "";
DPkg::Pre-Install-Pkgs "";
DPkg::Pre-Install-Pkgs:: "/usr/sbin/dpkg-preconfigure --apt || true";
DPkg::Post-Invoke "";
DPkg::Post-Invoke:: "if [ -x /usr/sbin/localepurge ] && [ $(ps w -p $PPID | grep -c remove) != 1 ]; then /usr/sbin/localepurge; else exit 0; fi";
-- /etc/apt/preferences --
Package: *
Pin: release a=experimental
Pin-Priority: 101
-- /etc/apt/sources.list --
# This file was automatically generated by apt-ping tool.
# Don't edit it manually. If you want to add or remove
# some repository, edit /etc/apt/ping.list instead
# then run apt-ping to generate this file again
deb http://ftp.ch.debian.org/debian/ stable main contrib non-free
deb-src http://ftp.ch.debian.org/debian/ stable main contrib non-free
deb http://ftp.ch.debian.org/debian/ unstable main contrib non-free
deb-src http://ftp.ch.debian.org/debian/ unstable main contrib non-free
deb http://ftp.ch.debian.org/debian/ testing main contrib non-free
deb-src http://ftp.ch.debian.org/debian/ testing main contrib non-free
deb http://ftp.ch.debian.org/debian/ experimental main contrib non-free
deb-src http://ftp.ch.debian.org/debian/ experimental main contrib non-free
deb http://www.debian-multimedia.org sid main
#Google chrome
deb http://dl.google.com/linux/deb/ stable main
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.31odino (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages apt depends on:
ii debian-archive-keyring 2009.01.31 GnuPG archive keys of the Debian a
ii libc6 2.10.1-5 GNU C Library: Shared libraries
ii libgcc1 1:4.4.2-2 GCC support library
ii libstdc++6 4.4.2-2 The GNU Standard C++ Library v3
apt recommends no packages.
Versions of packages apt suggests:
pn apt-doc <none> (no description available)
ii aptitude 0.6.0.1-1 terminal-based package manager (te
ii bzip2 1.0.5-3 high-quality block-sorting file co
ii dpkg-dev 1.15.4.1 Debian package development tools
ii lzma 4.43-14 Compression method of 7z format in
ii python-apt 0.7.13.3 Python interface to libapt-pkg
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.9.5
On Wed, May 23, 2012 at 12:47 AM, Vincent Lefevre <vincent@vinc17.net> wrote:
> On 2012-05-22 00:06:42 +0200, David Kalnischkies wrote:
>> + * apt-pkg/contrib/mmap.cc:
>> + - have a dummy SyncToFd around in case of ReadOnly access to a
>> + compressed file as we otherwise on Close() do not delete[] the
>> + char buffer but munmap() it… (Closes: #673815)
> ^^^^^^
>
> This is not one of the bugs 554387, 670401, 673065. Is this an error
> or are these bugs the same one, in which case a merge is missing?
Ah, damn. And i wondered why i managed to do so many control@
messages without a single error in the last few days…
Obviously to make up for this i had to use the wrong id in the close tag.
The text applies to the bug here and is fixed with 0.9.5.
The close applies to a bug(group) fixed in 0.9.4.
(Its the one about nagios and a pre-depends-break loop)
As i am already writing something, lets be correct: 670401 is titled:
rred segfaults during apt-get update if pkgcache.bin is corrupted
That was never true, as this file isn't even open at that point in time.
It's regenerated at the end of the 'apt-get update' run only.
Nowadays it is discarded unchecked, in earlier versions a broken
file could have made apt segfault -- but as said, not in rred.
Previous rred versions (read: in 2009) segfaulted properly because
of a too big file (5000kb!). I at least remember dealing with such
a problem (i think it was a too deep recursion).
The code was rewritten completely in the meantime,
so the initial bugreport is very likely fixed for a while. And the
bugreport itself was taken over by this new bug which just happened
to manifest itself in rred - hence i am closing this one with it.
Best regards
David Kalnischkies
--- End Message ---
Reply to: