Tobias, Tobias Krais wrote:
Debian Sid / Windows
At least on Linux you should be able to get meaningful stack traces.
Yesterday I tried many thing to get a deadlock and really bad things (deleting OOo program files,...) but OOo continued working. Then I gave up and just reinstalled and opened a new document, forgot the document and used it and then it deadlocked (for luck, I needed one for testing). Thats the story :-). Back to your question: I can't find out a special procedure to get a deadlock and thus I can't provide stack traces of the threads. I'm sorry. As soon as I catch one, I'll post it.
If you are on Linux, and the office deadlocks, just try # to get your process id ps -e | grep soffice.bin # to attach to the deadlocked process gdb -p <soffice.pid> # let gdb list you the threads (gdb) info threads 6 Thread -1503736912 (LWP 14887) 0xffffe410 in __kernel_vsyscall () 5 Thread -1538745424 (LWP 14890) 0xffffe410 in __kernel_vsyscall () 4 Thread -1547273296 (LWP 14891) 0xffffe410 in __kernel_vsyscall () 3 Thread -1557767248 (LWP 14892) 0xffffe410 in __kernel_vsyscall () .... # switch to every thread and get a stack trace (gdb) t 6 [Switching to thread 6 (Thread -1503736912 (LWP 14887)) ... (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xa7030fec in pthread_cond_timedwait@@GLIBC_2.3.2 () ... #2 0xa703145d in [EMAIL PROTECTED] () from ... ....
Greetings, Tobias
Kay --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
