https://bugs.freedesktop.org/show_bug.cgi?id=57071
--- Comment #12 from Alex Thurgood <ipla...@yahoo.co.uk> --- (In reply to comment #11) > Roman: is Valgrind useable on MacOs? > If yes callgrind part could be useful. > Could you launch this? > valgrind --tool=callgrind --simulate-cache=yes --dump-instr=yes > ./soffice.bin --splash-pipe=0 <path_to_log_file> > Since it'll be launched from Valgrind, LO will be about 80 times slower so > you need to be patient. Once you've got the freeze, wait for some minutes > and kill the process > (Log may be quite huge) Hi Julien, Unfortunately, valgrind is mostly unusable on OSX - even if you install it via the ports mechanism, the developers warn that it doesn't really work very well... from http://valgrind.org : "X86/Darwin and AMD64/Darwin (Mac OS X 10.6 and 10.7, with limited support for 10.8)." from http://www.sealiesoftware.com/valgrind/ This port is UNSUPPORTED and INCOMPLETE and BUGGY. It may not find bugs in your program, or run your program correctly, or run your program at all. So, the situation is not so good there. I tried running it once or twice on some master builds while looking into a few bugs in 3.4 development, but in its current state it is hopeless as a tool for a QAer on Mac. Alex -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
