Your message dated Sat, 8 Aug 2015 18:52:24 +0200 with message-id <[email protected]> and subject line Re: [Aptitude-devel] Bug#794830: aptitude: segfaults in memory allocation has caused the Debian Bug report #794830, regarding aptitude: segfaults in memory allocation 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.) -- 794830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794830 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: aptitude Version: 0.7-1 Severity: important Dear Maintainer, Since upgrade to 0.7, aptitude's TUI has become unusable for me due to consistent crashes, in particular occuring: 1. if I set the package tree limit, in either view 2. if I perform a search 2. if I open the menu bar (^T) and repeatedly change between menus. Repeatedly opening and closing the menu bar also works. In case of the search, it is interesting to note that it still seems to correctly perform the live-search while typing the query, but crashes upon OKing the dialog, but not when pressing Cancel. OKing a failed search only crashes after performing doing repeatedly. The CLI operation appears unaffected so far. Most crashes are segfaults at: #0 0x00007ffff5a63b15 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff5a64ef8 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007ffff5a67080 in malloc () from /lib/x86_64-linux-gnu/libc.so.6 #3 cwidget::util::transcode_buffer (...) at transcode.cc:99 #4 cwidget::util::transcode (...) at transcode.cc:249 #5 transcode (...) at transcode.h:48 #6 cwidget::util::transcode (...) at transcode.cc:270 (rest of traceback varies) However setting the limit in hierarchical view segfaults at: #0 0x00007ffff5a64538 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 deallocate (...) at /usr/include/c++/5/ext/new_allocator.h:110 #2 deallocate (...) at /usr/include/c++/5/bits/alloc_traits.h:386 #3 _M_destroy (...) at /usr/include/c++/5/bits/basic_string.h:185 #4 _M_dispose (...) at /usr/include/c++/5/bits/basic_string.h:180 #5 ~basic_string (...) at /usr/include/c++/5/bits/basic_string.h:544 #6 ~pkg_subtree_with_order (...) at ../../src/pkg_grouppolicy.cc:62 occasionally instead of a segv I get an abort preceded by the message: munmap_chunk(): invalid pointer Let me know if you want full tracebacks or other data. -- Package-specific info: Terminal: xterm-new $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.7 compiled at Aug 5 2015 18:53:06 Compiler: g++ 5.2.1 20150730 Compiled against: apt version 4.16.0 NCurses version 5.9 libsigc++ version: 2.4.1 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 5.9.20150516 cwidget version: 0.5.17 Apt version: 4.16.0 aptitude linkage: linux-vdso.so.1 (0x00007ffd7dbe2000) libapt-pkg.so.4.16 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.16 (0x00007f045432b000) libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x00007f04540f5000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007f0453eca000) libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x00007f0453cc4000) libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x00007f04539c5000) libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007f04536f7000) libboost_iostreams.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.58.0 (0x00007f04534de000) libxapian.so.22 => /usr/lib/libxapian.so.22 (0x00007f04530dc000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f0452ebe000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f0452b43000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f0452842000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f045262b000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0452282000) libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f045207f000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f0451e7a000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f0451c5f000) libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007f0451a4f000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f045182b000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f0451623000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f045141d000) /lib64/ld-linux-x86-64.so.2 (0x000055da5879d000) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1-3.dmz.1-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_NL.UTF-8, LC_CTYPE=en_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages aptitude depends on: ii aptitude-common 0.7-1 ii libapt-pkg4.16 1.0.10.1 ii libboost-iostreams1.58.0 1.58.0+dfsg-3 ii libc6 2.19-19 ii libcwidget3v5 0.5.17-3.1 ii libgcc1 1:5.2.1-14 ii libncursesw5 5.9+20150516-2 ii libsigc++-2.0-0c2a 2.4.1-1 ii libsqlite3-0 3.8.11.1-1 ii libstdc++6 5.2.1-14 ii libtinfo5 5.9+20150516-2 ii libxapian22v5 1.2.21-1.2 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc] 0.7-1 ii libparse-debianchangelog-perl 1.2.0-5 ii sensible-utils 0.0.9 Versions of packages aptitude suggests: pn apt-xapian-index <none> pn debtags <none> pn tasksel <none> -- no debconf information
--- End Message ---
--- Begin Message ---Version: 0.7-1+b1 Hi, Axel Beckert wrote: > Matthijs van Duin wrote: > > On 8 August 2015 at 01:18, Axel Beckert <[email protected]> wrote: > > > Matthijs: I'd close this bug with 0.7-1+b1 if you confirm. > > > > The crashes are gone indeed. > > Yay! Closing this bug hence. > > The... cosmetic... issue I mailed you about is still present. Should I > > file a new bug report on that? > > Yes, please. Please also include in which kind of terminal emulator > you run aptitude as I can reproduce this with "pbuilder login" running > inside an uxterm. *sigh* Small but misleading typo: "I can reproduce this" should have been "I can't reproduce this" as I cannot reproduce the issues shown in the animated GIF. Please file a new bug report for them if you can still reproduce them. Regards, Axel -- ,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
--- End Message ---
_______________________________________________ Aptitude-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
