Bug#819840: [Aptitude-devel] Bug#819840: aptitude: Segfaults if suspended and foregrounded on virtual linux console

2016-04-24 Thread Manuel A. Fernandez Montecelo
2016-04-23 21:54 Axel Beckert: 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. Yeah, that's what I had understood. In fact, waiting for "press key to continue" ignores the

Bug#819840: [Aptitude-devel] Bug#819840: aptitude: Segfaults if suspended and foregrounded on virtual linux console

2016-04-23 Thread Axel Beckert
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

Bug#819840: [Aptitude-devel] Bug#819840: aptitude: Segfaults if suspended and foregrounded on virtual linux console

2016-04-08 Thread Manuel A. Fernandez Montecelo
2016-04-06 01:22 Axel Beckert: Not sure if it's gdb which is broken on armhf or something else. Did you try with valgrind, btw? 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. Other than that, I

Bug#819840: [Aptitude-devel] Bug#819840: aptitude: Segfaults if suspended and foregrounded on virtual linux console

2016-04-05 Thread Axel Beckert
Hi again, > It's possibly the first time I did this with an aptitude version > released after Jessie. So I can't tell when it started, except that it > didn't happen with Debian Jessie on armhf nor with Raspian Jessie. I'm > not sure about Raspbian Stretch, but I may have used aptitude (0.7.5) >