Apache OpenOffice (AOO) Bugzilla – Issue 17844
OOo crashes when trying to access a MyODBC data-source without a valid URL
Last modified: 2006-05-31 14:29:06 UTC
OOo exits abruptly during setup of a MyODBC connection. The crash occurs when the user selects a MySQL data-source, then tries to select the "Tables" tab of the DataSources Administration dialog (or the tables tree-item) *before* selecting a valid MySQL URL. If you select the correct URL before trying to view/edit any tables things work OK. Thus, this is a not a major problem.
bryan, thanks for reporting this. However, I cannot reproduce this :(. I tried both RC1 and RC2 .... Are you using MySQL via JDBC or ODBC? fs->clu: can you reproduce this?
I'm using all RedHat-9.0 rpms for MySQL, MyODBC, unixODBC. ...err... I just tried this on another RH9.0 box running OOo-1.1beta2 and I can't reproduce the bug. I've got the same MySQL/MyODBC rpms installed on both systems. I just upgraded to OOo-1.1rc (the same version that shows the 'bug' on my other machine) as well with no problems. I've no idea what causes the problem on my local machine. If no-one can reproduce the problem, I guess we should end this thread! thanks for looking into it, though. cheers, Bryan
No, don't end the thread -- if you can still reproduce the problem, please get a stack trace! If the builtin crash reporter doesn't pop up, then please use gdb to get a backtrace; see http://kegel.com/openoffice/#dump
Turns out my last post was mistaken: The second system I tested which *did not* show the bug wasn't RH9.0 afterall, but rh8.0. I've since been able to reproduce the crash on my RH9.0 home system. It is real afterall! To reproduce the bug on OOo-1.1rc1, RH9.0 with MyODBC etc.: 1) Open a Writer document and open the Data-Sources window 2) Open the Administrate Data Sources dialog and click "New Data Source" 3) Set the Database Type -> MySQL 4) Click the "Tables" tab (or select Tables from the tree) ... at this point OOo exits with the following stack dump: [bryan@bryan program]$ ./swriter Fatal exception: Signal 11 Stack: /home/bryan/OpenOffice.org1.1/program/libsal.so.3[0x40bb2e2a] /home/bryan/OpenOffice.org1.1/program/libsal.so.3[0x40bb2fb4] /home/bryan/OpenOffice.org1.1/program/libsal.so.3[0x40bb307a] /lib/tls/libpthread.so.0[0x411277c8] /usr/lib/libmyodbc.so(SQLDriverConnect+0x5a0)[0x499645f0] /usr/lib/libodbc.so.1(SQLDriverConnect+0x46a)[0x4990b04a] /home/bryan/OpenOffice.org1.1/program/libodbcbase2.so(_ZN12connectivity4odbc11OConnection14OpenConnectionERKN3rtl8OUStringElh+0x1d8)[0x496128c6] /home/bryan/OpenOffice.org1.1/program/libodbcbase2.so(_ZN12connectivity4odbc11OConnection9ConstructERKN3rtl8OUStringERKN3com3sun4star3uno8SequenceINS8_5beans13PropertyValueEEE+0xaea)[0x4961376e] /home/bryan/OpenOffice.org1.1/program/libodbcbase2.so(_ZN12connectivity4odbc10ODBCDriver7connectERKN3rtl8OUStringERKN3com3sun4star3uno8SequenceINS8_5beans13PropertyValueEEE+0x2ed)[0x4961031f] /home/bryan/OpenOffice.org1.1/program/libmysql2.so[0x498aa85d] /home/bryan/OpenOffice.org1.1/program/libdbpool2.so[0x49573b81] /home/bryan/OpenOffice.org1.1/program/libdbpool2.so[0x49573744] /home/bryan/OpenOffice.org1.1/program/libdbpool2.so[0x49570b9c] /home/bryan/OpenOffice.org1.1/program/libdbu645li.so[0x4931a59e] /home/bryan/OpenOffice.org1.1/program/libdbu645li.so[0x49226eaf] /home/bryan/OpenOffice.org1.1/program/libsfx645li.so(_ZN12SfxTabDialog15ActivatePageHdlEP10TabControl+0x3c5)[0x454f29c5] /home/bryan/OpenOffice.org1.1/program/libsfx645li.so(_ZN12SfxTabDialog23LinkStubActivatePageHdlEPvS0_+0x26)[0x454f25f8] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN10TabControl12ActivatePageEv+0x25)[0x4027ec5d] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN10TabControl13SelectTabPageEt+0x73)[0x4027f5ad] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN10TabControl15MouseButtonDownERK10MouseEvent+0x42)[0x4027d964] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_Z20ImplHandleMouseEventP6Windowthllmtt+0xff3)[0x40225dc5] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_Z19ImplWindowFrameProcPvP8SalFrametPKv+0x16a)[0x402286c0] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN12SalFrameData16HandleMouseEventEP7_XEvent+0x445)[0x40286ec5] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN12SalFrameData8DispatchEP7_XEvent+0x123)[0x40288ce9] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN10SalDisplay8DispatchEP7_XEvent+0x28f)[0x402b4919] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN10SalDisplay5YieldEh+0xf1)[0x402b4667] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so[0x402b0647] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN7SalXLib5YieldEh+0x426)[0x402af21a] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN11SalInstance5YieldEh+0x34)[0x402b7f70] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN11Application5YieldEv+0x61)[0x400e53c9] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN6Dialog7ExecuteEv+0x1dc)[0x401d6666] /home/bryan/OpenOffice.org1.1/program/libsfx645li.so(_ZN12SfxTabDialog7ExecuteEv+0x42)[0x454f145e] /home/bryan/OpenOffice.org1.1/program/libdbu645li.so[0x4925514b] /home/bryan/OpenOffice.org1.1/program/libsvt645li.so(_ZN3svt17OGenericUnoDialog7executeEv+0x2a9)[0x406de53b] /home/bryan/OpenOffice.org1.1/program/libdbu645li.so[0x492f6206] /home/bryan/OpenOffice.org1.1/program/libdbu645li.so[0x492f8ed2] /home/bryan/OpenOffice.org1.1/program/libdbu645li.so[0x4930a811] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so[0x40224d8f] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_Z20ImplHandleMouseEventP6Windowthllmtt+0x125b)[0x4022602d] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_Z19ImplWindowFrameProcPvP8SalFrametPKv+0x16a)[0x402286c0] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN12SalFrameData16HandleMouseEventEP7_XEvent+0x445)[0x40286ec5] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN12SalFrameData8DispatchEP7_XEvent+0x123)[0x40288ce9] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN10SalDisplay8DispatchEP7_XEvent+0x28f)[0x402b4919] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN10SalDisplay5YieldEh+0xf1)[0x402b4667] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so[0x402b0647] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN7SalXLib5YieldEh+0x426)[0x402af21a] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN11SalInstance5YieldEh+0x34)[0x402b7f70] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN11Application5YieldEv+0x61)[0x400e53c9] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_ZN11Application7ExecuteEv+0x35)[0x400e52db] /home/bryan/OpenOffice.org1.1/program/soffice.bin(_ZN7desktop7Desktop4MainEv+0x1acc)[0x8064eac] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(_Z6SVMainv+0x49)[0x400ea197] /home/bryan/OpenOffice.org1.1/program/libvcl645li.so(main+0x1c)[0x402adb7c] /lib/tls/libc.so.6(__libc_start_main+0xe4)[0x420156a4] /home/bryan/OpenOffice.org1.1/program/soffice.bin(_ZN6Window11RequestHelpERK9HelpEvent+0x3d)[0x805e311] Aborted [bryan@bryan program]$ cheers, Bryan
Hi Bryan, I remember to heard about a bug in the unixODBC libs. Which version do you use? And may be if you aren't using the newest one, could you please test if this works. Thanks, Ocke
He's using MyODBC, not UnixODBC; they are different, I think. Bryan, looks like you have found a bug in MyODBC. Can you take it up with the MyODBC folks and report back here with what they say? They'll probably be very happy to get a crash report from you for a reproducible crash, and will be able to provide a fix.
I know, but unixODBC is the layer OOo is talking to and unixODBC then talks to MyODBC. Best regards, Ocke PS: OOo.org | unixODBC | MyODBC or PostgreSQL or any kind of ODBC driver
Shows what I know. BTW, everyone may already know this, but here are some guides to testing this combination: redhat 7.3: http://www.unixodbc.org/doc/OOoMySQL.pdf redhat 9: http://www.unixodbc.org/doc/OOoMySQL9.pdf
Red Hat 9 uses the following: MyODBC-2.50.39-11.i386.rpm unixODBC-2.2.3-6.i386.rpm Since unixODBC-2.2.6 is the one with the bugfix in it, I'd say the reporter really needs to upgrade to UnixODBC-2.2.6. Unless he can reproduce it there, we should consider this a problem in his 'old' version of UnixODBC. I'm marking this bug as INVALID to reflect that fact. Bryan, feel free to reopen this issue if you can still reproduce after upgrading to UnixODBC-2.2.6 and/or report this issue to the UnixODBC team. Thanks!
looks like dan has predicted (problem with older version) - so i close this bug CLU->bryan: feel free to reopen, if you still have a problem with it
.
change subcomponent to 'none'