Le 30/11/2016 à 16:48, Jean-Marc Lasgouttes a écrit :
a useless backtrace
If you have the symbols at hand, then you can get them by hand. For
instance if you have compiled in debug mode, then you can run gdb as you
do usually, only after the fact, and get the symbols with "info symbols
0x123
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 cod
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 o
邮件已收到，谢谢。保持联系！
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 0x000105aac141
