Your message dated Sun, 2 Mar 2014 17:31:30 +0000 with message-id <capq4b8kmiwdihor_7ek1ktub7ogwxr_j2a01n-52omknzak...@mail.gmail.com> and subject line Re: [Aptitude-devel] Bug#668544: Unreproducible has caused the Debian Bug report #668544, regarding aptitude hangs with full cpu load. 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.) -- 668544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668544 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: aptitude Version: 0.6.6-1 Severity: normal Hello: I've lately experienced a 100% cpu load by aptitude. I wouldn't be able to point a specific cause, but it seems the conflict resolver is involved. I've attached gdb when aptitude hanged and I'm inlining the backtrace I get: 0x0000000000605c99 in unlink (x=0x1ae7c10) at /usr/include/boost/multi_index/detail/hash_index_node.hpp:72 warning: Source file is more recent than executable. 72 while(y->next()!=x){y=y->next();} (gdb) bt #0 0x0000000000605c99 in unlink (x=0x1ae7c10) at /usr/include/boost/multi_index/detail/hash_index_node.hpp:72 #1 unlink (x=0x1ae7be0) at /usr/include/boost/multi_index/hashed_index.hpp:1021 #2 erase_ (x=0x1ae7be0, this=0x9c4bd0) at /usr/include/boost/multi_index/hashed_index.hpp:727 #3 erase_ (x=0x1ae7be0, this=0x9c4bc0) at /usr/include/boost/multi_index_container.hpp:529 #4 final_erase_ (x=0x1ae7be0, this=0x9c4bd0) at /usr/include/boost/multi_index/detail/index_base.hpp:155 #5 erase (position=..., this=0x9c4bd0) at /usr/include/boost/multi_index/hashed_index.hpp:282 #6 boost::flyweights::hashed_factory_class<boost::flyweights::detail::refcounted_value<boost::flyweights::detail::default_value_policy<generic_solver_information<aptitude_universe>::choice_set_with_hash>::rep_type, generic_solver_information<aptitude_universe>::choice_set_with_hash>, generic_solver_information<aptitude_universe>::choice_set_with_hash, generic_solver_information<aptitude_universe>::hash_choice_set_with_hash, mpl_::na, mpl_::na>::erase (this=0x9c4bc0, h=0x1ae7be0) at /usr/include/boost/flyweight/hashed_factory.hpp:77 #7 0x0000000000605e44 in erase<bool (*)(boost::flyweights::detail::refcounted_handle<boost::flyweights::detail::refcounted_value<boost::flyweights::detail::default_value_policy<generic_solver_information<aptitude_universe>::choice_set_with_hash>::rep_type, generic_solver_information<aptitude_universe>::choice_set_with_hash> const*, boost::flyweights::detail::flyweight_core_tracking_helper<boost::flyweights::detail::default_value_policy<generic_solver_information<aptitude_universe>::choice_set_with_hash>, mpl_::na, boost::flyweights::refcounted, boost::flyweights::hashed_factory<generic_solver_information<aptitude_universe>::hash_choice_set_with_hash, mpl_::na, mpl_::na, 0>, boost::flyweights::simple_locking, boost::flyweights::static_holder> > const&)> (check=<optimized out>, h=...) at /usr/include/boost/flyweight/detail/flyweight_core.hpp:70 #8 ~refcounted_handle (this=0x23bf4a8, __in_chrg=<optimized out>) at /usr/include/boost/flyweight/refcounted.hpp:113 #9 ~flyweight (this=0x23bf4a8, __in_chrg=<optimized out>) at /usr/include/boost/flyweight/flyweight.hpp:115 #10 generic_solver_information<aptitude_universe>::~generic_solver_information (this=0x23bf4a0, __in_chrg=<optimized out>) at ../../../../src/generic/problemresolver/search_graph.h:53 #11 0x0000000000605f61 in ~pair (this=0x23bf470, __in_chrg=<optimized out>) at /usr/include/c++/4.6/bits/stl_pair.h:87 #12 _Destroy<std::pair<generic_choice<aptitude_universe>, generic_solver_information<aptitude_universe> > > (__pointer=0x23bf470) at /usr/include/c++/4.6/bits/stl_construct.h:94 #13 __destroy<std::pair<generic_choice<aptitude_universe>, generic_solver_information<aptitude_universe> >*> (__last=<optimized out>, __first=0x23bf470) at /usr/include/c++/4.6/bits/stl_construct.h:104 #14 _Destroy<std::pair<generic_choice<aptitude_universe>, generic_solver_information<aptitude_universe> >*> (__last=0x23bf4c0, __first=<optimized out>) at /usr/include/c++/4.6/bits/stl_construct.h:127 #15 _Destroy<std::pair<generic_choice<aptitude_universe>, generic_solver_information<aptitude_universe> >*, std::pair<generic_choice<aptitude_universe>, generic_solver_information<aptitude_universe> > > (__last=0x23bf4c0, __first=<optimized out>) at /usr/include/c++/4.6/bits/stl_construct.h:153 #16 ~vector (this=0x23e9d90, __in_chrg=<optimized out>) at /usr/include/c++/4.6/bits/stl_vector.h:350 ---Type <return> to continue, or q <return> to quit--- #17 generic_dep_solvers<aptitude_universe>::~generic_dep_solvers (this=0x23e9d90, __in_chrg=<optimized out>) at ../../../../src/generic/problemresolver/search_graph.h:315 #18 0x0000000000614fdb in ~rep_type (this=0x23e9d90, __in_chrg=<optimized out>) at /usr/include/boost/flyweight/detail/default_value_policy.hpp:34 #19 ~refcounted_value (this=0x23e9d90, __in_chrg=<optimized out>) at /usr/include/boost/flyweight/refcounted.hpp:50 #20 destroy<boost::flyweights::detail::refcounted_value<boost::flyweights::detail::default_value_policy<generic_d At this point if I proceed with a finish command in gdb, gdb will never take back control of the application and will eventually either crash or finish (end) aptitude. I also can provide a state bundle (~50MB) on request. This bug looks similar to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629266 but since that one is tagged for squeeze and I'm on sid I chose to file a new bug report. Please let me know if I can help to debug this issue. Regards, -- Package-specific info: Terminal: xterm $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.6.6 compiled at Mar 27 2012 22:36:24 Compiler: g++ 4.6.3 Compiled against: apt version 4.10.1 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.10.1 aptitude linkage: linux-vdso.so.1 => (0x00007fffaefff000) libapt-pkg.so.4.10 => /usr/lib/libapt-pkg.so.4.10 (0x00007fa9097d1000) libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x00007fa9095a2000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007fa909379000) libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0x00007fa909174000) libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0x00007fa908e6c000) libept.so.1 => /usr/lib/libept.so.1 (0x00007fa908c0f000) libxapian.so.22 => /usr/lib/libxapian.so.22 (0x00007fa908812000) libz.so.1 => /usr/lib/x86_64-linux-gnu/libz.so.1 (0x00007fa9085fc000) libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007fa908354000) libboost_iostreams.so.1.48.0 => /usr/lib/libboost_iostreams.so.1.48.0 (0x00007fa90813b000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa907f1f000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fa907c17000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa907995000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa90777f000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa9073f7000) libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007fa9071f4000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa906ff0000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fa906dea000) libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007fa906bda000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fa9069d1000) /lib64/ld-linux-x86-64.so.2 (0x00007fa909b11000) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.13 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages aptitude depends on: ii apt [libapt-pkg4.10] 0.8.15.10 ii libboost-iostreams1.48.0 1.48.0-3 ii libc6 2.13-27 ii libcwidget3 0.5.16-3.1 ii libept1 1.0.5 ii libgcc1 1:4.7.0-3 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-3 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 0.45 ii aptitude-doc-en [aptitude-doc] 0.6.6-1 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 ---2014-02-21 23:19 GMT+00:00 Manuel A. Fernandez Montecelo <[email protected]>: > 2014-02-21 21:17 GMT+00:00 Raúl Sánchez <[email protected]>: >> >> To be honest, I can't remember the exact operation, I remember it was 100% >> reproducible. I somehow expected aptitude-run-bundle was enough to reproduce. >> >> [...] >> I'm not sure if with these steps I did something wrong, but unfortunately I >> couldn't reproduce the problem either. I ran out of ideas, sorry. > > [...] > > I also tried it and didn't observe any problem with it. So yeah, I > would say that the bug can be closed. Closing now, thanks. -- 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
