Why does my UNO component crash OpenOffice.org, while the sample UNO component runs fine?
There is a known bug in the office, see #i13377#, which was not fixed for OpenOffice.org1.1. The office in general crashes, when a python script leads to an unhandled exception (for example an attribute error). You may try to workaround this bug by adding a try: except: level in your trigger() implementation, which dumps an error message to stdout/stderr, but sadly this will not help in all cases (for example compilation failure for some reason, please follow the issue for further information). Of course, there may be other reasons for a crash, you will only know, when you try to retrieve a native callstack (for example by using gdb).
Related Questions
- I am applying to the Dual-Degree Program in Art History and Arts Administration. What do I need to know about the writing sample component of the application?
- What is the sample size for a particular data item, questionnaire section, examination component, or laboratory analyte?
- Where Can I Fine A Sample Mission Statement For The Garment Industry?
