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

[Manuel A. Fernandez Montecelo]

2016-03-05 21:16 GMT+00:00 Katsuhiko Nishimra <ktns.87 at gmail.com>:
> I've confirmed with aptitude=0.7.8-1 that SIGABRT has gone even when
> quitting without accepting a solution.

Good, thanks for the feed-back.

BTW, it is strange that the other problem was not reported before, the
problem has ben present for many years (much longer than the last
stable).  I guess that not many people use this feature, or they don't
mind about it crashing, or they don't bother submitting a bug report
:)


> However, I've encountered another corner case.
> When aptitude cause too many conflicts and cannot resolve them in
> command line mode,
> (I ran into this situation because I installed aptitude=0.7.8-1 by dpkg
> and forgot upgrading aptitude-dbgsym accordingly, then tested
> $ aptitude -s install -t experimental ~i)
> entering curses mode by hitting `e' and quitting without resolving
> conflicts kills aptitude by SIGABRT.
>
> This is a very irregular situation, so I won't reopen this bug report.

It might be good to submit a new report about this problem -- maybe it
affects not-so-unusual scenarios.  If you can get a backtrace,
doubleplus good.

(I could try to reproduce myself, but I'm quite constrained by
bandwidth at the moment, and if you can reproduce it reliably it can
give a good hint about where to start to look).


> Again, many thanks for your effort.

You're welcome :)

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