To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=55602
Issue #:|55602
Summary:|Exception handling in UNO component leads to crash
Component:|udk
Version:|680
Platform:|PC
URL:|
OS/Version:|Linux
Status:|NEW
Status whiteboard:|
Keywords:|
Resolution:|
Issue type:|DEFECT
Priority:|P3
Subcomponent:|code
Assigned to:|tbo
Reported by:|sb
------- Additional comments from [EMAIL PROTECTED] Fri Oct 7 02:52:00 -0700
2005 -------
At least with the Sun-built unxlngi6 OOo, a C++ UNO component built with almost
any recent GCC crashes when it uses exception handling:
If the component is built on a system with glibc2 version 2.2.4 or higher (which
is typically the case nowadays), any kind of exception handling within the
component (even a simple "try{throw 1;}catch(...){}") leads to program abort.
The main reason is that the libgcc_s.so.1 that we ship as part of the Sun-built
OpenOffice.org 2.0 is built against glibc2 version 2.2.0 instead of glibc2
version 2.2.4. (A second reason may be that the GCC version used to build
SO8/OOo2.0, namely 3.4.1, and the GCC version used to build the C++ UNO
component are too different, but that is much more unlikely.) For whatever
reason, this problem went unnoticed for a long time, and only recently got
reported independently two times (see
<http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=14564> and
<http://api.openoffice.org/servlets/ReadMsg?list=dev&msgNo=13384>).
Attached is a component.uno.so (and a source.tgz) to reproduce the problem on
unxlngi6.pro: In soffice, use "Tools > Package Manager... > Add..." to add
component.uno.so to "My Packages". Then use "Tools > Macros > Organize Macros >
OpenOffice.org Basic > Edit" to write a simple Basic script
dim a() as string
createunoservice("test.Component").run(a)
When exectuing the script without this issue fixed, the soffice will crash or an
error message will show up that the URP connection to the component has been
lost (when the component has been started out of process on the first run).
When executing the script with this issue fixed, the script will run
successfully without any side effects.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
