Description of problem: Tcl's TDBC Mysql client stops working after upgrade to mariadb-connector-c-3.2.7-1.fc35.x86_64. Tclsh core dumps when connecting to the database. Version-Release number of selected component (if applicable): mariadb-connector-c-3.2.7-1.fc35.x86_64 How reproducible: Steps to Reproduce: 1. Upgrade to mariadb-connector-c-3.2.7-1.fc35.x86_64 2. Use some tcl code to connect to mariadb and perform a simple query. 3. Actual results: Tclsh core dumps. Expected results: Tclsh to run Additional info: Downgrading to mariadb-connector-c-3.1.13-2.fc35.x86_64 works
I tried to research further the problem, and I have created a bug also in tdbc::mysql: https://core.tcl-lang.org/tdbcmysql/tktview/430e4ff9df6e5077cc54876c33d3a2a35520021a The problem seems to be that the mariadb client reports as version "30207". What is mysql_get_client_version() supposed to return? What did the previous package (3.1.*) returned?
Hi George, There was a change in the CONC/C 3.2.0: https://jira.mariadb.org/browse/CONC-509 https://github.com/mariadb-corporation/mariadb-connector-c/commit/a37b7c3965706f9a062baaba0c494dd6efb2c306 https://mariadb.com/kb/en/mariadb-connector-c-320-release-notes/ It was actually a fix of a long term wrong behaviour, where the connector reported version of the server, instead of itself. So this is something the upstream of tbdc::mysql has to adopt. Thank you for creating the upstream tracker. -- Is there anything more I can help you with? Is the tdbc::mysql piece of software you are using a Fedora package I can look into? (or is it 3rd party software?)
I think it is a third-party package, and its maintenairs need to find a way to understand whether mysql/mariadb library is loaded, and check the appropriate version.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.