https://bugs.documentfoundation.org/show_bug.cgi?id=100994
--- Comment #14 from Alex Thurgood <ipla...@yahoo.co.uk> ---
(In reply to corrado from comment #11)
> please explain how to do and I do it
>
> corrado
Hmm, well the usual way would be to find and download a debug-enabled build of
master source code tree from here :
http://dev-builds.libreoffice.org/daily/master/
However, there don't appear to be any debug-enabled builds in any of the Mac
machine directories at present, so you are going to be stuck unless you can
build LibreOffice yourself from source.
If you do manage to get hold of a recent debug-enabled build for OSX, you can
try running it in a lldb debugging session.
>From the Terminal.app console :
lldb /Applications/LibreOfficeDev.app
wait for lldb to start and initialize the debugging environment, then at the
lldb prompt, type :
run
and LibreOffice will try and start. If it fails to starts, messages will be
displayed on the console output. If you get a message like SIGSEGV or SIGABRT,
you could try typing :
bt all
and pressing enter. It might take some time to produce output on the screen, so
be patient. When the output has stopped appearing on the console, you can copy
and paste the whole ouptu into a text file, and then attach that file to this
bug report.
You can quit a lldb session by typing :
q
and you will be asked if you want to quit the running process (assuming that LO
is indeed still running).
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
