https://bugs.documentfoundation.org/show_bug.cgi?id=103077
--- Comment #30 from Howard Johnson <bridgeportcontrac...@gmail.com> ---
A couple of answers to your comments:
(In reply to Lionel Elie Mamane from comment #20)
> I wouldn't be too surprised if the MariaDB libmaodbc didn't implement
> SQLGetInfo(... SQL_FILE_USAGE ...)
> or did it incorrectly.
It's in odbc_3_api.c:
SQLRETURN SQL_API SQLGetInfo(SQLHDBC ConnectionHandle,
SQLUSMALLINT InfoType,
SQLPOINTER InfoValuePtr,
SQLSMALLINT BufferLength,
SQLSMALLINT *StringLengthPtr)
{
MADB_Dbc *Dbc= (MADB_Dbc *)ConnectionHandle;
SQLRETURN ret;
if (!Dbc)
return SQL_INVALID_HANDLE;
MADB_CLEAR_ERROR(&Dbc->Error);
MDBUG_C_ENTER(Dbc, "SQLGetInfo");
MDBUG_C_DUMP(Dbc, InfoType, d);
ret= Dbc->Methods->GetInfo(Dbc, InfoType, InfoValuePtr, BufferLength,
StringLengthPtr, FALSE);
MDBUG_C_RETURN(Dbc, ret, &Dbc->Error);
}
> The "Driver" and "Setup" entries are inconsistent: you use driver from
> MariaDB, but setup from MySQL; I wonder it that's not the source of the
> crash. Please try to use *both* from MariaDB, no mixing.
Good point. I found that MariaDB doesn't offer a ODBC setup driver.
I apologize for neglecting to mention that LO Base is also crashing when trying
to connect with MDBTools ODBC driver. I didn't focus on this because I thought
it might just make things too complicated and perhaps we should just deal with
one crash at a time. Note that MDBTools uses the exact same library (one
library) as both the driver and setup library.
Later today I hope to take an ODBC call trace of the similar MDBTools crash,
and compare it with the MariaDB ODBC call trace crash.
Anyway this setup library you mention appears to only be used by the unixODBC
tools to setup/configure odbc.ini and odbcinst.ini. (But I'm not 100% sure.)
In other words, if it's missing I can't use those tools, (the gui ODBC
configuration tools, or odbcinst). But that notwithstanding isql works when
the setup library is missing.
I wasn't sure what to do when I found the setup library missing but decided a
reasonable idea was to use the mysql one, and it worked. So I'm not 100% sure,
but I think the setup libaray only helps setup the configuration parameters in
these two confiburation files (/etc/odbc.ini and /etc/odbcinst.ini). I think
that would also make sense because ALL of the setup libraries (except for
MDTTools) are named something like: xxxxxS.lo. (With a "S").
> The backtrace would be far more useful if you installed the libreoffice-dbg
> package (same version as your installed LibreOffice), or used a debug
> version of libreoffice, e.g. from one of the directories that ends with
> "-dbg" at http://dev-builds.libreoffice.org/daily/master/ (since these are
> builds of master / alpha versions, exercice care and caution).
I will work on this. Sorry I am slow in responding. I am new to Linux and
having to learn much to proceed little. Thanks for your help!
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
