Re: MySQL + ODBC Seg Fault

Graham Fenner <[email protected]> writes:

>I am using cryptlib with mysql and myodbc driver on linux.  I make a simple
>certificate as described in the manual, I then open a ODBC database using
>KeySetOpen .... i checked return errors and they are not returning bad , its
>just that when i call
>
>AddPublicKey(keyset,cryptCertificate).
>
>This is a high level function and it will connect to the database. Okay the
>OPTION which is set on KeySetOpen is NONE because i want it to write.  Well,
>when i call AddPublicKey i get a segmentation fault.  I used gdb to debug the
>problem, it seems that mysqlclient is calling Escape function. Like so :
>
>escape_string_for_mysql () from
>/usr/lib/libmysqlclient_r.so.16
>
>This is where dbg found the segmentation fault signal.

This sounds like a bug in the MyODBC driver and/or MySQL if it's happening
inside libmysqlclient, so you'd have to file a bug report against them.
cryptlib checks for the presence of MySQL in keyset/odbc.c in order to work
around some existing MySQL/MyODBC bugs, but this is one that no-one's
encountered before.

Peter.

_______________________________________________
Cryptlib mailing list
[email protected] via Mail: [email protected]
Archive: ftp://ftp.franken.de/pub/crypt/cryptlib/archives/
http://news.gmane.org/gmane.comp.encryption.cryptlib
Posts from non-subscribed addresses are blocked to prevent spam, please
subscribe in order to post messages.