To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108953
                 Issue #|108953
                 Summary|Conflict between libldap50.so and libldap2
               Component|Word processor
                 Version|OOo 3.0.1
                Platform|PC
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|writerneedsconfirm
             Reported by|eymux2009





------- Additional comments from [email protected] Thu Feb  4 13:50:11 
+0000 2010 -------
We are experiencing regular SIGSEGVs of the OOo JVM. From the stacktrace it can
be seen, that the error happens during access of LDAP user data. Even though OOo
includes its own LDAP library (libldap50.so from Mozilla), it is making calls to
libldap_r.so, which is part of libldap2 (OpenLDAP). But the last call of strtok,
which is the cause of the crash, is not within libldap_r.so (I checked the
sources), but in libldap50.so. We assume that dynamic linking of those libraries
is the culprit here, beacuse both libraries share some identical function names.
This bug is related to Bug 292127 in the Mozilla bug tracker
(https://bugzilla.mozilla.org/show_bug.cgi?id=292127). The stacktraces attached
to this bug clearly show the mixed calls in both libraries.

---------------------------------------------------------------------
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]

Reply via email to