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

Bug#349233: marked as done (apt: Segmentation faulty tree... 50%)



Your message dated Wed, 13 Apr 2011 12:42:39 +0200
with message-id <20110413124201.GA12114@debian.org>
and subject line Re: Bug#93453: segfaults after caculating dependancy tree.
has caused the Debian Bug report #93453,
regarding apt: Segmentation faulty tree... 50%
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.)


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

REASONING for grave

apt-get becomes unusable to the whole system. Can't install, remove or
query any information.

PROBLEM

Without any notice (under testing) apt-get stopped working and 
printing message

  Segmentation faulty tree... 50%

I've done some GOOGLING and it seems this bug has been seen before,
but no intelligent handling has been added to apt. See bug Bug#84277
where  Jason Gunthorpe <jgg@debian.org> writes:

    > apt-get segfaults w/out (in my opinion) any reason:

    This has always been traced back to file corruption in /var/cache/apt/*.bin

    If you can erase those files and run the apt command and have it work then
    that is definately the problem.

    Nobody has ever been able to reproduce it, unless they have buggy hardware
    :>

    Jason

This machine does not not have buggy hardware; apt has been working fine
from the start.

SUGGESTION:

As it seems that apt-get is able to start (and does not segfault),
would it be possible to add a signal handler or error handler that -
when encountering this problem - would print a messsage:

  Hm, I suspect corrupted data files. Please delete
  /var/cache/apt/*.bin followed by "apt-get update" to reset apt.

Which indeed fixed this error condition.

-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (/etc/apt/sources.list present, but not submitted) --


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.14-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)

Versions of packages apt depends on:
ii  libc6                         2.3.5-12   GNU C Library: Shared libraries an
ii  libgcc1                       1:4.0.2-7  GCC support library
ii  libstdc++6                    4.0.2-7    The GNU Standard C++ Library v3

Versions of packages apt recommends:
pn  debian-archive-keyring        <none>     (no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Closing this bug, as it is not really something that can
be fixed in APT.

On Tue, Apr 10, 2001 at 09:51:14AM +1000, Brian May wrote:
> Package: apt
> Version: 0.5.3
> Severity: normal
> 
> (note: recompiled for stable; same version works fine on other
> computer)
> 
> snoopy:~# chroot  /nfsroot/potato/root/
> snoopy:/# apt-get upgrade
> Reading Package Lists...
> Building Dependency Tree...
> Segmentation fault
>  
> snoopy:/# gdb apt-get
> GNU gdb 19990928
> Copyright 1998 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 "i686-pc-linux-gnu"...
> (no debugging symbols found)...
> (gdb) set args upgradwe
> (gdb) set args upgrade 
> (gdb) r
> Starting program: /usr/bin/apt-get upgrade
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> Reading Package Lists...
> Building Dependency Tree...
> (no debugging symbols found)...
> Program received signal SIGSEGV, Segmentation fault.
> 0x400736af in pkgProblemResolver::MakeScores ()
>    from /usr/lib/libapt-pkg-libc6.1-3-2.so.3.1
> (gdb) bt
> #0  0x400736af in pkgProblemResolver::MakeScores ()
>    from /usr/lib/libapt-pkg-libc6.1-3-2.so.3.1
> #1  0x400756ad in pkgProblemResolver::ResolveByKeep ()
>    from /usr/lib/libapt-pkg-libc6.1-3-2.so.3.1
> #2  0x40072fec in pkgAllUpgrade () from /usr/lib/libapt-pkg-libc6.1-3-2.so.3.1
> #3  0x80572fb in strcpy ()
> #4  0x40059d4a in CommandLine::DispatchArg ()
>    from /usr/lib/libapt-pkg-libc6.1-3-2.so.3.1
> #5  0x80619c0 in strcpy ()
> #6  0x40163a52 in __libc_start_main () from /lib/libc.so.6
> 
> 
> Steps to try and fix (with no sucess):
> 
> 1. upgrade from 0.5.0 to 0.5.3
> 
> 2. try same image on different computers (NFS-Root). I think
> chroot should be most reliable. In any case I get the same error
> everywhere.
> 
> 3. tried combinations of -s, install, and -d, but always get the same error.
> 
> 4. created an /etc/apt/preferences file. Same as what is used on
> a working system:
> 
> Package: autoconf
> Pin: release a=stable
> Pin-Priority: 1001
> 
> Package: automake
> Pin: release a=stable
> Pin-Priority: 1001
> 
> Package: libtool
> Pin: release a=stable
> Pin-Priority: 1001
> 
> Package: *
> Pin: release a=stable
> Pin-Priority: 600
> 
> Package: *
> Pin: release a=potato
> Pin-Priority: 600
> 
> Package: *
> Pin: release o=helix
> Pin-Priority: 700
> 
> Possibly something is currupt on this root directory, but I don't
> know what (everything looks OK to me), and even if that is the
> case, apt-get should not segfault.
> 
> I think I saw something at one stage with apt-get from stable about the
> status file being currupt. I looked at that file, and it looks fine.
> Nor does dpkg have any problems accessing it. I can send it to you on
> request. However, I think it might be just a false lead.
> 
> -- System Information
> Debian Release: 2.2
> Architecture: i386
> Kernel: Linux snoopy 2.4.3 #1 Sat Mar 31 13:50:13 EST 2001 i686
> 
> Versions of packages apt depends on:
> ii  libc6                        2.1.3-17    GNU C Library: Shared libraries an
> ii  libstdc++2.10                1:2.95.2-13 The GNU stdc++ library            
> 
> 
> 

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

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

Attachment: pgpuhSSBikV3M.pgp
Description: PGP signature


--- End Message ---

Reply to: