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

Bug#670401: marked as done (aptitude: segmentation fault after (during?) update)

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 aptitude: segmentation fault after (during?) update
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 --- 
Package: aptitude
Version: 0.6.6-1+b1
Severity: normal

Dear Maintainer,
launching aptitude update,

Get: 23 http://ftp.se.debian.org experimental/main amd64 2012-04-25-0814.20.pdiff [716 B]
Get: 24 http://ftp.se.debian.org sid/main 2012-04-25-0814.20.pdiff [4368 B]     
Get: 25 http://ftp.se.debian.org experimental/non-free amd64 Packages [3238 B]                    
Get: 26 http://ftp.se.debian.org experimental/main 2012-04-25-0814.20.pdiff [298 B]                       
Ign http://ftp.sunet.se unstable/main Translation-it_IT                  
Ign http://ftp.sunet.se unstable/main Translation-it
Ign http://ftp.sunet.se unstable/main Translation-en
Get: 27 http://ftp.se.debian.org sid/non-free 2012-04-25-0814.20.pdiff [598 B]
Get: 28 http://ftp.se.debian.org sid/main amd64 2012-04-25-0814.20.pdiff [4892 B]
Scaricato 643 kB in 4s (154 kB/s)               
E: Method rred has died unexpectedly!
E: Il sottoprocesso rred ha ricevuto un segmentation fault.


-- Package-specific info:
Terminal: xterm
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.6.6 compiled at Apr 16 2012 22:17:55
Compiler: g++ 4.6.3
Compiled against:
  apt version 4.12.0
  NCurses version 5.9
  libsigc++ version: 2.2.10
  Ept support enabled.
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 5.9.20110404
  cwidget version: 0.5.16
  Apt version: 4.12.0

aptitude linkage:
	linux-vdso.so.1 =>  (0x00007fffb1bff000)
	libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 (0x00007fe24bf70000)
	libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x00007fe24bd41000)
	libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007fe24bb18000)
	libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0x00007fe24b913000)
	libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0x00007fe24b613000)
	libept.so.1.0.5.4.12 => /usr/lib/libept.so.1.0.5.4.12 (0x00007fe24b3c0000)
	libxapian.so.22 => /usr/lib/libxapian.so.22 (0x00007fe24afc3000)
	libz.so.1 => /usr/lib/x86_64-linux-gnu/libz.so.1 (0x00007fe24adad000)
	libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007fe24ab05000)
	libboost_iostreams.so.1.49.0 => /usr/lib/libboost_iostreams.so.1.49.0 (0x00007fe24a8ec000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fe24a6d0000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fe24a3c8000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fe24a146000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fe249f30000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fe249ba8000)
	libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007fe2499a5000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fe2497a1000)
	libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007fe249590000)
	libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fe24938b000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fe249182000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fe24c2c1000)

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.3.2a (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages aptitude depends on:
ii  libapt-pkg4.12            0.9.2
ii  libboost-iostreams1.49.0  1.49.0-2
ii  libc6                     2.13-30
ii  libcwidget3               0.5.16-3.2
ii  libept1.4.12              1.0.6.1
ii  libgcc1                   1:4.7.0-4
ii  libncursesw5              5.9-6
ii  libsigc++-2.0-0c2a        2.2.10-0.1
ii  libsqlite3-0              3.7.11-2
ii  libstdc++6                4.7.0-4
ii  libtinfo5                 5.9-6
ii  libxapian22               1.2.8-1
ii  zlib1g                    1:1.2.6.dfsg-2

Versions of packages aptitude recommends:
ii  apt-xapian-index                <none>
ii  aptitude-doc-en | aptitude-doc  <none>
ii  libparse-debianchangelog-perl   1.2.0-1
ii  sensible-utils                  0.0.6

Versions of packages aptitude suggests:
ii  debtags  <none>
ii  tasksel  3.09

-- 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: