https://bugs.freedesktop.org/show_bug.cgi?id=79979
--- Comment #4 from Stephan Bergmann <[email protected]> --- So in both comment 0 and comment 3 what apparently happens is that libc's malloc detects a problem and its malloc_printerr then causes the process to hang. In both cases, what could be helpful to find out the root cause that caused malloc to detect a problem would be the output already produced by malloc_printerr, plus the full backtrace of the thread on which malloc detected the problem (which, among other things, makes it clear whether or not its the main thread), ideally the full backtrace of all threads. Another venue of attack, of course, is to use tools like Valgrind to get at the cause of the malloc problem. -- 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
