[Aptitude-devel] Bug#816322: aptitude: SIGABRT due to assertion failure when quitting from conflict resolver

[Manuel A. Fernandez Montecelo]

Control: tags -1 + moreinfo unreproducible


Hi,

2016-02-29 20:46 Katsuhiko Nishimra:
>Package: aptitude
>Version: 0.7.6-1
>Severity: important
>
>Dear Maintainer,
>
>I've run into a SIGABRT when quitting a conflict resolver in aptitude-
>curses.
>
>How to reproduce:
>* Invoke conflicts by something like
>  $ aptitude -st experimental full-upgrade
>* Enter the conflict resolver by hitting `e'
>* Terminate the process by hitting `qqy'
>* Then it goes:
>   aptitude:
>/usr/include/boost/flyweight/detail/recursive_lw_mutex.hpp:72:boost::flyweights::detail::recursive_lightweight_mutex::scoped_lock::scoped_lock(boost::flyweights::detail::recursive_lightweight_mutex&):
>Assertion `pthread_mutex_lock(&m_)==0' failed.
>   Ouch!  Got SIGABRT, dying..
>
>A report on launchpad below might be related with this.
>https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1435175

2016-02-29 21:03 Katsuhiko Nishimra:
>Package: aptitude
>Version: 0.6.11-1+b1
>
>Dear maintainer,
>I've confirmed this is also found in jessie.

I could not reproduce it in my systems with the same versions, with
either mini-buffer option enabled (as you seem to have) or disabled.

Does this happen to you with .7 as well, uploaded earlier today?

Weird boost problems have happened in the past in aptitude, especially
with flyweight, but I haven't seen them recently myself or in other bug
reports.


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>