Your message dated Sun, 1 Jan 2017 05:00:45 +0100
with message-id <[email protected]>
and subject line Re: aptitude: #839792 (Segfaults when typing (into aptitude)
during or maybe shortly before package download) and #837366 (Crash when typing
while saying "Updating ... and quitting") might be related
has caused the Debian Bug report #839792,
regarding aptitude: Segfaults when typing (into aptitude) during or maybe
shortly before package download
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.)
--
839792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839792
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.8.3-1+b1
Hi,
I can reproducible make aptitude crash with a segmentation fault if I
press "b" during (or maybe shortly before) the package download. I also
tried a few other keys like e.g. "n" or "/". Also crashes. Even pressing
"q" crashes.
Two backtraces, both caused by pressing "b":
Core was generated by `aptitude -u'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fb7f9d97720 in _xend () at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
33 ../sysdeps/unix/sysv/linux/x86/elision-unlock.c: No such file or
directory.
[Current thread is 1 (Thread 0x7fb7f7517700 (LWP 14883))]
(gdb) bt
#0 0x00007fb7f9d97720 in _xend () at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
#1 __lll_unlock_elision (lock=0x7fb7fafe2360
<cwidget::toplevel::input_thread::input_event_mutex>, private=0)
at ../sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#2 0x00007fb7fad3cb9a in cwidget::toplevel::input_thread::operator()() () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#3 0x00007fb7fad3cbc1 in void*
cwidget::threads::thread::bootstrap<cwidget::threads::bootstrap_proxy<cwidget::toplevel::input_thread>
>(void*) ()
from /usr/lib/x86_64-linux-gnu/libcwidget.so.3
#4 0x00007fb7f9d8c464 in start_thread (arg=0x7fb7f7517700) at
pthread_create.c:333
#5 0x00007fb7f923397f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105
(gdb)
Core was generated by `aptitude'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007ff988859720 in _xend () at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
33 ../sysdeps/unix/sysv/linux/x86/elision-unlock.c: No such file or
directory.
[Current thread is 1 (Thread 0x7ff985fd9700 (LWP 17166))]
(gdb) bt
#0 0x00007ff988859720 in _xend () at
../sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
#1 __lll_unlock_elision (lock=0x7ff989aa4360
<cwidget::toplevel::input_thread::input_event_mutex>, private=0)
at ../sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#2 0x00007ff9897feb9a in cwidget::toplevel::input_thread::operator()() () from
/usr/lib/x86_64-linux-gnu/libcwidget.so.3
#3 0x00007ff9897febc1 in void*
cwidget::threads::thread::bootstrap<cwidget::threads::bootstrap_proxy<cwidget::toplevel::input_thread>
>(void*) ()
from /usr/lib/x86_64-linux-gnu/libcwidget.so.3
#4 0x00007ff98884e464 in start_thread (arg=0x7ff985fd9700) at
pthread_create.c:333
#5 0x00007ff987cf597f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105
(gdb)
-- Package-specific info:
Terminal: eterm-color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude
aptitude version information:
aptitude 0.8.3
Compiler: g++ 6.2.0 20160914
Compiled against:
apt version 5.0.0
NCurses version 6.0
libsigc++ version: 2.10.0
Gtk+ support disabled.
Qt support disabled.
Current library versions:
NCurses version: ncurses 6.0.20160917
cwidget version: 0.5.17
Apt version: 5.0.0
aptitude linkage:
linux-vdso.so.1 (0x00007fffa57e1000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
(0x00007fb1a86e6000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5
(0x00007fb1a84b6000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5
(0x00007fb1a828c000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
(0x00007fb1a8085000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3
(0x00007fb1a7d88000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
(0x00007fb1a7a83000)
libboost_iostreams.so.1.61.0 =>
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.61.0 (0x00007fb1a786b000)
libboost_filesystem.so.1.61.0 =>
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.61.0 (0x00007fb1a7652000)
libboost_system.so.1.61.0 =>
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.61.0 (0x00007fb1a744e000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30
(0x00007fb1a7042000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007fb1a6e25000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007fb1a6aa2000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fb1a679e000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007fb1a6587000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb1a61e9000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fb1a5fe5000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2
(0x00007fb1a5dce000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fb1a5bb1000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0
(0x00007fb1a59a1000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fb1a577e000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1
(0x00007fb1a556c000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fb1a5364000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fb1a515d000)
/lib64/ld-linux-x86-64.so.2 (0x000055688f3ba000)
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'),
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1,
'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages aptitude depends on:
ii aptitude-common 0.8.3-1
ii libapt-pkg5.0 1.3.1
ii libboost-filesystem1.61.0 1.61.0+dfsg-2.1+b1
ii libboost-iostreams1.61.0 1.61.0+dfsg-2.1+b1
ii libboost-system1.61.0 1.61.0+dfsg-2.1+b1
ii libc6 2.24-3
ii libcwidget3v5 0.5.17-4+b1
ii libgcc1 1:6.2.0-5
ii libncursesw5 6.0+20160917-1
ii libsigc++-2.0-0v5 2.10.0-1
ii libsqlite3-0 3.14.2-1
ii libstdc++6 6.2.0-5
ii libtinfo5 6.0+20160917-1
ii libxapian30 1.4.0-2
Versions of packages aptitude recommends:
ii libparse-debianchangelog-perl 1.2.0-10
ii sensible-utils 0.0.9
Versions of packages aptitude suggests:
ii apt-xapian-index 0.48
ii aptitude-doc-en [aptitude-doc] 0.8.3-1
ii debtags 2.1.2
pn tasksel <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8.4-1
Hi Manuel,
Manuel A. Fernandez Montecelo wrote:
> 2016-10-10 23:13 Axel Beckert:
> > JFTR: in case this is actually an issue inside cwidget or in the way
> > cwidget is used by aptitude, the two bug reports 839792 (Segfaults
> > when typing (into aptitude) during or maybe shortly before package
> > download) and #837366 (Crash when typing while saying "Updating ...
> > and quitting") might be the same issue or at least related.
>
> With an up-to-date unstable and 0.8.4-1, I cannot reproduce this
> (neither of them). Can you still reproduce it?
I can neither reproduce #839792 nor #837366 with 0.8.4-1 anymore,
hence closing both. Thanks for the heads up!
> It seems to me that these recurrent problems involving cwidget, events,
> typing and threads have something to do either with the specific locale
> settings (mine are the ones below) or temporary ABI incompatibilities,
> perhaps due to binNMU recompilations and different order of compilation
> of boost, sigc++, cwidget and aptitude. Something similar to what
> happened with the Big GCC5 C++11 ABI break, just at a smaller scale.
Sounds likely.
> # env | grep LANG
> LANG=en_GB.UTF-8
> LANGUAGE=en_GB:en
JFTR: Looks similar here:
# env | grep LANG
LANGUAGE=en_GB:en
LANG=C.UTF-8
> Another idea would be a difference between using the minibuffer and not
> using it.
Yeah, except that at least with pressing "b" or "u", no minibuffer is
involved. (But yes, minibuffer often has been the key difference if I
have an issue and you never run into it. :-)
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
