Your message dated Tue, 1 Sep 2015 00:41:56 +0100
with message-id 
<capq4b8kr+1qosc8qnjwnej3dhq9un9t3wpyademmq_rrpum...@mail.gmail.com>
and subject line segfault in aptitude::why::target::generate_successors()
has caused the Debian Bug report #562053,
regarding segfault in aptitude::why::target::generate_successors()
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 [email protected]
immediately.)


-- 
562053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562053
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.4.11.11-1+b2
Severity: normal


aptitude crashes with this command line: 

aptitude why-not libguile-dev

This is what valgrind shows: 

==14962== Memcheck, a memory error detector
==14962== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==14962== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright 
info
==14962== Command: aptitude why-not libguile-dev
==14962== 
==14962== Invalid read of size 1
==14962==    at 0x40E0B3D: debVersioningSystem::CheckDep(char const*, int, char 
const*) (in /usr/lib/libapt-pkg-libc6.9-6.so.4.8.1)
==14962==    by 0x814DFFA: 
aptitude::why::target::generate_successors(aptitude::why::justification const&, 
std::deque<aptitude::why::justification, 
std::allocator<aptitude::why::justification> >&, aptitude::why::search_params 
const&, int) const (cmdline_why.cc:517)
==14962==    by 0x814EE46: aptitude::why::(anonymous 
namespace)::justification_search::next(std::vector<aptitude::why::action, 
std::allocator<aptitude::why::action> >&) (cmdline_why.cc:113)
==14962==    by 0x8150122: do_why(std::vector<aptitude::matching::pkg_matcher*, 
std::allocator<aptitude::matching::pkg_matcher*> > const&, 
pkgCache::PkgIterator const&, int, bool, bool&) (cmdline_why.cc:893)
==14962==    by 0x81518F4: do_why(std::vector<aptitude::matching::pkg_matcher*, 
std::allocator<aptitude::matching::pkg_matcher*> > const&, 
pkgCache::PkgIterator const&, int, bool) (cmdline_why.cc:988)
==14962==    by 0x8151CEC: cmdline_why(int, char**, char const*, int, bool) 
(cmdline_why.cc:1136)
==14962==    by 0x805F751: main (main.cc:615)
==14962==  Address 0x9e27d6dc is not stack'd, malloc'd or (recently) free'd
==14962== 
==14962== 
==14962== Process terminating with default action of signal 11 (SIGSEGV)
==14962==  Access not within mapped region at address 0x9E27D6DC
==14962==    at 0x40E0B3D: debVersioningSystem::CheckDep(char const*, int, char 
const*) (in /usr/lib/libapt-pkg-libc6.9-6.so.4.8.1)
==14962==    by 0x814DFFA: 
aptitude::why::target::generate_successors(aptitude::why::justification const&, 
std::deque<aptitude::why::justification, 
std::allocator<aptitude::why::justification> >&, aptitude::why::search_params 
const&, int) const (cmdline_why.cc:517)
==14962==    by 0x814EE46: aptitude::why::(anonymous 
namespace)::justification_search::next(std::vector<aptitude::why::action, 
std::allocator<aptitude::why::action> >&) (cmdline_why.cc:113)
==14962==    by 0x8150122: do_why(std::vector<aptitude::matching::pkg_matcher*, 
std::allocator<aptitude::matching::pkg_matcher*> > const&, 
pkgCache::PkgIterator const&, int, bool, bool&) (cmdline_why.cc:893)
==14962==    by 0x81518F4: do_why(std::vector<aptitude::matching::pkg_matcher*, 
std::allocator<aptitude::matching::pkg_matcher*> > const&, 
pkgCache::PkgIterator const&, int, bool) (cmdline_why.cc:988)
==14962==    by 0x8151CEC: cmdline_why(int, char**, char const*, int, bool) 
(cmdline_why.cc:1136)
==14962==    by 0x805F751: main (main.cc:615)
==14962==  If you believe this happened as a result of a stack
==14962==  overflow in your program's main thread (unlikely but
==14962==  possible), you can try to increase the size of the
==14962==  main thread stack using the --main-stacksize= flag.
==14962==  The main thread stack size used in this run was 8388608.
==14962== 
==14962== HEAP SUMMARY:
==14962==     in use at exit: 8,944,336 bytes in 4,630 blocks
==14962==   total heap usage: 485,291 allocs, 480,661 frees, 39,624,199 bytes 
allocated
==14962== 
==14962== LEAK SUMMARY:
==14962==    definitely lost: 40 bytes in 1 blocks
==14962==    indirectly lost: 120 bytes in 10 blocks
==14962==      possibly lost: 4,529,099 bytes in 3,123 blocks
==14962==    still reachable: 4,415,077 bytes in 1,496 blocks
==14962==         suppressed: 0 bytes in 0 blocks
==14962== Rerun with --leak-check=full to see details of leaked memory
==14962== 
==14962== For counts of detected and suppressed errors, rerun with: -v
==14962== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 45 from 8)
Killed

Also, when running apt-get upgrade or apt-get dist-upgrade, the package 
guile-1.8-dev is reported as being "held back" for some reason.


-- Package-specific info:
aptitude 0.4.11.11 compiled at Aug  3 2009 17:14:11
Compiler: g++ 4.3.3
Compiled against:
  apt version 4.8.0
  NCurses version 5.7
  libsigc++ version: 2.0.18
  Ept support enabled.

Current library versions:
  NCurses version: ncurses 5.7.20090803
  cwidget version: 0.5.16
  Apt version: 4.8.1
        linux-gate.so.1 =>  (0xb7f56000)
        libapt-pkg-libc6.9-6.so.4.8 => /usr/lib/libapt-pkg-libc6.9-6.so.4.8 
(0xb7e76000)
        libncursesw.so.5 => /lib/libncursesw.so.5 (0xb7e32000)
        libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0xb7e2b000)
        libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0xb7d68000)
        libept.so.0 => /usr/lib/libept.so.0 (0xb7ced000)
        libxapian.so.15 => /usr/lib/libxapian.so.15 (0xb7b9c000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb7b87000)
        libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xb7b6e000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7a7c000)
        libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb7a56000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7a39000)
        libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb78f2000)
        libutil.so.1 => /lib/i686/cmov/libutil.so.1 (0xb78ee000)
        libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb78e9000)
        /lib/ld-linux.so.2 (0xb7f57000)
Terminal: xterm
$DISPLAY is set.
`which aptitude`: /usr/bin/aptitude
aptitude version information:

aptitude linkage:

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6. 0.7.23.1          Advanced front-end for dpkg
ii  libc6                  2.10.2-2          GNU C Library: Shared libraries
ii  libcwidget3            0.5.16-2          high-level terminal interface libr
ii  libept0                0.5.29            High-level library for managing De
ii  libgcc1                1:4.4.2-3         GCC support library
ii  libncursesw5           5.7+20090803-2    shared libraries for terminal hand
ii  libsigc++-2.0-0c2a     2.0.18-2          type-safe Signal Framework for C++
ii  libstdc++6             4.4.2-3           The GNU Standard C++ Library v3
ii  libxapian15            1.0.17-1          Search engine library
ii  zlib1g                 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages aptitude recommends:
ii  aptitude-doc-en [aptitude-do 0.4.11.11-1 English manual for aptitude, a ter
ii  libparse-debianchangelog-per 1.1.1-2     parse Debian changelogs and output

Versions of packages aptitude suggests:
pn  debtags                       <none>     (no description available)
ii  tasksel                       2.80       Tool for selecting tasks for insta

-- no debconf information



--- End Message ---
--- Begin Message ---
Hello,

As the trace says, debVersioningSystem is part of libapt, maybe it was
a temporary failure there or a mismatch in ABI between apt and
aptitude.

As a means to try to reproduce it anyway, I am running in a loop
picking random names of packages, and asking "aptitude why-not
${package}" and "aptitude why ${package}", and I have not seen any
crash so far (hundreds/thousands of packages processed after many
minutes running).  Of course, I tried libguile-dev first, and
everything is fine on this end.

It is almost impossible to do anything with this bug report right now.
So I think that it is better to close this report now, sorry that it
was not handled in a more timely manner.


Cheers.
-- 
Manuel A. Fernandez Montecelo <[email protected]>

--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

Reply via email to