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

Bug#554387: /usr/bin/apt-get: segmentation fault when trying to update



retitle 554387 rred segfaults during apt-get update if pkgcache.bin is corrupted
found 554387 0.9.1
thanks

On Wed, 04 Nov 2009 at 09:04:49 +0100, Salvo Tomaselli wrote:
> E: Method rred has died unexpectedly!
> E: Il sottoprocesso rred ha ricevuto un segmentation fault.
> 
> rred[15924]: segfault at bf498fe4 ip b7c5c8af sp bf498fe8 error 6 in libc-2.10.1.so[b7bf5000+141000]

I saw a similar crash recently:

Apr 20 09:51:53 reptile kernel: [309153.324154] rred[2731]: segfault at 1d71148 ip 00007ffae2176799 sp 00007ffff95ec270 error 4 in libc-2.13.so[7ffae20fc000+17d000]

On Tue, 19 Jul 2011 at 12:53:43 +0200, Michal Suchanek wrote:
> This happens when the pkgcache is corrupted (eg due to update with too
> low disk space).

Removing /var/cache/apt/*.bin* seems to have resolved it. I have 26G free
on my root filesystem (which also contains /var), so it must have been corrupt
for some other reason?

(Sorry, I deleted the corrupt versions before I realised they'd probably
have been useful to the apt developers...)

This is on my development laptop (running unstable, frequently upgraded since
lenny), so it's had basically every version of apt that was available and is
currently on 0.9.1.

It would be useful if apt could recover from this sort of thing without
sysadmin intervention - if the cache is indeed just a cache, it should be
safe to get rid of it and go back to the source files whenever something
is not right?

    S



Reply to: