Hennes Rohling - Sun Germany - ham02 - Hamburg wrote:
open a command shell 'cd' to OOo installation program directory and type
'crashrep soffice.exe'.

The crash reporter should come up and takes a snapshot of the process. Provide your email address and send a crashreport. Contact [EMAIL PROTECTED] to search for your report in the database.

Great! It works for sending a crash report.

Does anyone know how to search for the report?

Unfortunately snapshots of blocked process canot be processed automaticly because it's not possible to find duplicates because the stacks of all threads will never be the same and it's hard to find an algorythm to determine which of the threads is responsible for the freeze.

Hmm, that sounds difficult to find the cause.

The teacher who reported the frozen of soffice.exe gave additional information:
 - OOo1.1.3 on Windows Me
 - Samba 2.2.8a Japanese on RedHat7.2
 - Every students access to the file server through network drive U:
 - The number of client machine on which OOo is running is more than 30.

 - A file that a student specified was not created at all.
 - He didn't look at appearance of the status bar on OOo as the frozen happened.

Regards,
Tora


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to