[Aptitude-devel] Bug#819840: Bug#819840: aptitude: Segfaults if suspended and foregrounded on virtual linux console
Manuel A. Fernandez Montecelo
manuel.montezelo at gmail.com
Mon Apr 25 01:06:37 UTC 2016
2016-04-23 21:54 Axel Beckert:
>did I mention that this issue is TUI related? Haven't really tried to
>suspend aptitude in commandline mode while it's waiting for me to
>press enter or such.
Yeah, that's what I had understood. In fact, waiting for "press key to
continue" ignores the Ctrl-Z.
>Manuel A. Fernandez Montecelo wrote:
>> >Not sure if it's gdb which is broken on armhf or something else.
>> Did you try with valgrind, btw?
>Nope. Will try on the Raspberry Pi when I'm back home.
>> In armhf unusably slow I suppose, but in x86 is usable (~1 minute).
>> I think that you can redirect valgrind's stderr and still use
>While I still can reproduce the issue with aptitude 0.8 on armhf
>(about a day ago), I (to some extent unfortunately) can no more
>reproduce it on amd64 (now).
>Interestingly I have another phenomenon with Ctrl-Z on amd64 now:
You always get strange behaviours! (midway between :D and :/)
>On a linux vt console it only works once: I can suspend aptitude once
>with Ctrl-Z and foreground it again with "fg". But from then on,
>Ctrl-Z seems to be a no-op inside aptitude's TUI. Works fine though in
>an xterm or a screen session (inside the same xterm).
I can always suspend repeatedly also with the latest version (and my
compiled version from master and other flags like debugging enabled),
both in xterms and Linux VT.
Also with aptitude inside tmux after ssh inside an xterm (konsole).
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>
More information about the Aptitude-devel