On 7 August 2015 at 09:22, Axel Beckert <a...@debian.org> wrote: > This one is probably in aptitude itself. So they're probably different > issue. Keeping them in one bug report for the moment, though, until > someone can pinpoint the cause more precise than me.
It appears to be memory corruption, so crashes showing up elsewhere is probably just fallout. I tried running it under valgrind, and thanks to the extra space it reserves around allocated regions I could now set the package limit without crashing. It also resulted in a logfile full of memory access errors. I don't know anything about the structure of aptitude or cwidget but this may be something to look at. (I'd never used valgrind before but it turned out to be a simple matter of "valgrind aptitude 2>logfile") -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
