Hi Manuel,
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.
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
> curses.
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:
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).
> If I can reproduce it there will be a better chance to fix it,
> otherwise I'm totally in the dark and without any clues.
Sure. I'll update this bug report as soon as I have some further hints
on this. Hints from others experiencing the same issue are of course
welcome, too. (Actually they're even wanted! ;-)
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, 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
