On Wed, Nov 30, 2016 at 04:48:54PM +0100, Jean-Marc Lasgouttes wrote:

> Le 12/11/2016 à 16:55, Stephan Witt a écrit :
> > Hi fellows,
> > 
> > I've recently learned LyX has problems with clean crash management on Mac 
> > OS X.
> > 
> > The first problem is the call stack printing feature. The code tries to 
> > provide a
> > demangled stack trace but unfortunately this isn’t case on Mac.
> > 
> > Example of a crash report:
> > ( 1) 1 lyx 0x0000000105aac141 
> > _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwEEEESA_b
> >  : 1 lyx 0x0000000105aac141 
> > _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwEEEESA_b
> >  + 138
> > ( 2) 2 lyx 0x0000000105aac6c2 
> > _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwEEEESA_b
> >  : 2 lyx 0x0000000105aac6c2 
> > _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwEEEESA_b
> >  + 149
> [...]
> > 
> > I don’t know if it works on Linux but on Mac I’d like to see it disabled.
> > The builtin OSX-Crash-Reporter works much better.
> 
> Personally on Linux I get a useless backtrace without any symbol name, just
> addresses.

Can't we disable this for all platforms? It simply adds noise and when
investigating a crash bug I have to manually disable it for viewing
useful output in the terminal. Pretty please.

-- 
Enrico

Reply via email to