To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=107246
------- Additional comments from f...@openoffice.org Fri Nov 27 13:28:49 +0000 2009 ------- I think we have two problems here. One is that C/C++ (Connector/C++, the C++ component for connecting to a MySQL server, which is used by C/OOo, the extension) tries to connect via socket, though it's told to connect via host/port. Second, the fact that this crashs. C/C++ throws an exception when it cannot connect, and this exception is expected to be caught in C/OOo. Obviously, the catching does not happen, and that's the reason for the crash. Strange enough, there's a perfectly fitting "catch (sql::SQLException)" in mysqlc::OConnection::construct, but it doesn't work. This sounds to me (who I don't have much expertise in this area) as if we have a symbol name here. Exceptions are caught via RTTI mechanisms, and if the RTTI information for an exception is not properly exported from the lib which throws it, then it cannot be caught. What's the result of the following: > nm -D libmysqlcppconn.so | grep SQLException | c++filt > nm -D mysqlc.uno.so | grep SQLException | c++filt (to be done in the folder where the extension has been installed)? --------------------------------------------------------------------- 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
