pali

Hello! With specifying `dbi:mysql` in DSN string you are using `DBD::mysql` driver and not `DBD::MariaDB`. Please try again with DSN string `"DBD::MariaDB:$dbname;host=localhost"`.

I compiled DBD::MariaDB 1.21 with MariaDB 10.3.8 client and run your example script under valgrind to check for any memory corruption and also under gdb to see any suspicious problems:...

Hi! Have you able to reproduce this issue under gdb/valgrind with DBD::MariaDB?

Valgrind may prevent segfaults, but it prints stacktrace of any memory corruptions which could lead to segfaults. So it is still useful. I was trying to reproduce your reported issue...

@hashbangperl: I tried to reproduce this issue on Debian 10 Buster with MariaDB 10.3.18, but without success. There is no memory corruption, no crash.

Could you please provide gdb backtrace of the crash? I tried different test scenarios on Debian Buster but I was not able to trigger segfault.

@hashbangperl: Are you able to reproduce this problem?

I'm closing this issue as nobody was able to reproduce it for more years.

Hello @ibrierley! Meanwhile could you try [DBD::MariaDB](https://metacpan.org/pod/DBD::MariaDB) driver? We are running basic test suite of DBD::MariaDB driver compiled with new versions of MySQL and MariaDB clients against of the old...

If connecting with DBD::MariaDB fails too, could you provide perl code which you use to connect? And also whole output?