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

Bug#725401: marked as done (libapt-pkg4.12: Crash in pkgCache::DepIterator::IsIgnorable)

Your message dated Thu, 13 Aug 2015 09:56:27 +0200
with message-id <20150813095541.GA9510@debian.org>
and subject line Re: Bug#725401: libapt-pkg4.12: Crash in pkgCache::DepIterator::IsIgnorable
has caused the Debian Bug report #725401,
regarding libapt-pkg4.12: Crash in pkgCache::DepIterator::IsIgnorable
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.)


-- 
725401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725401
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libapt-pkg4.12
Version: 0.9.9.4
Severity: important

Dear Maintainer,

	Attempting to use aptitude or apt recently caused both programs to segfault during startup, (normal user, or root). GDB indicate sthe problem lies within the pkgCache handling. 


pkgCache::DepIterator::IsIgnorable(pkgCache::PrvIterator const&) const () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
(gdb) bt
#0  0x00007ffff7af369c in pkgCache::DepIterator::IsIgnorable(pkgCache::PrvIterator const&) const () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
#1  0x00007ffff7af7175 in pkgDepCache::CheckDep(pkgCache::DepIterator, int, pkgCache::PkgIterator&) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
#2  0x00007ffff7af7be8 in pkgDepCache::DependencyState(pkgCache::DepIterator&)
() from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
#3  0x00007ffff7afff0b in pkgDepCache::Update(OpProgress*) ()
from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
#4  0x00007ffff7b0043e in pkgDepCache::Init(OpProgress*) ()
from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12

	Examining with strace, I found that the program was crashing after opening the file /etc/apt/sources.list.d/autopkgtest.list. Removing this file prevented the crash.




-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libapt-pkg4.12 depends on:
ii  libbz2-1.0         1.0.6-5
ii  libc6              2.17-92
ii  libgcc1            1:4.8.1-2
ii  libstdc++6         4.8.1-2
ii  multiarch-support  2.17-92
ii  zlib1g             1:1.2.8.dfsg-1

libapt-pkg4.12 recommends no packages.

libapt-pkg4.12 suggests no packages.

-- no debconf information

deb file:///tmp/tmp.OHeFkZC10D/binaries/ /

--- End Message ---
--- Begin Message --- 
On Sun, Oct 06, 2013 at 01:57:30AM +0200, David Kalnischkies wrote:
> On Sat, Oct 5, 2013 at 12:26 PM, D Haley <mycae@gmx.com> wrote:
> > pkgCache::DepIterator::IsIgnorable(pkgCache::PrvIterator const&) const () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
> […]
> >         Examining with strace, I found that the program was crashing after opening the file /etc/apt/sources.list.d/autopkgtest.list. Removing this file prevented the crash.
> 
> These two claims conflict in so far as the file parsing is not done
> (or at least not for this bt-moment) anywhere near the IsIgnoreable call.
> 
> That disabling a source fixes the problem is more an indication of some
> pointer-magic going mad while the cache is created and later crashes
> appear "at random" at whoever follows the bad pointer/data.
> 
> $ ls -hl /var/cache/apt/*.bin
> 
> I presume both files are bigger than ~20 MB?
> 
> 
> Could you remove both files (as root) and (as normal user) run:
> $ apt-get -s -o APT::Cache-Start=200000000 whatever-command-segfaults-for-you
> (^ I really hope those files were smaller than 200 MB ;) )
> 
> Is it still segfaulting? (It shouldn't if I am right with my suspicion)
> 
> Beware also: Running with gdb can "fix" or delay the segfault, so try it with
> a core file and check that the segfault with gdb is actually the same you see
> without (the hidden cause is likely the same, but the backtrace might not).
> 
> Those segfaults tend to disappear with any change to the files parsed,
> so please create a backup of the files in /var/lib/apt/lists, any file://
> source you have and the file /var/lib/dpkg/status for later in any case.


Closing this now, as there was no reply since 2013, and it's
not reproducible.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

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

Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
    - If you don't I might ignore you.

--- End Message ---
Reply to: