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 updated all my unstable today and still no crash. It occured to me that maybe your crashes are caused by some config options that you have and are not default, e.g. mini-buffer IIRC. Most of the widgets use sigc++ and threads and so on, so maybe that's the reason why you can reproduce it consistently and I don't (I use almost always the defaults, except when checking things). You can try by moving the config away and see if it still crashes or not, then enabling the options one by one (esp. the ones related to widgets/interface). 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. Cheers. -- Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
