https://bugs.freedesktop.org/show_bug.cgi?id=57959
--- Comment #8 from Lionel Elie Mamane <[email protected]> --- SIGSEGV in java code are not necessarily a problem (when run under GDB). What happens is that the process/thread gets SIGSEGV, the JVM catches that and raises exception NullPointerException. The Java code can then cleanly catch the exception, handle the error condition and continue with no problem. You have to wait until it actually crashes :) When running LibreOffice under GDB with some Java thread, I do: handle SIGSEGV pass noprint nostop to stop gdb from giving me many false positives (false alarm). It it hits a problematic (e.g. in C++ code) SIGSEGV / uncaught Java NullPointerException, it will abort and gdb should still cache that. Else, the JVM creates a file with a backtrace that can give hints. It is useful when hunting for such problems to run libreoffice with --norestore, so that the abort happens sooner. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
