Aaron Trevena

> 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"`. Yes, I just copied the same test...

> 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...

I've managed to replicate it in GDB with DBD::mysql, but since reinstalling DBD::MariaDB I've not been able to get it to segfault, even when the mysql dbd client is, so...

Valgrind seems to prevent it happening, I was able to get it to fail with DBD::MariaDB initially with standard mariadb on buster *without* valgrind, it may be possible with GDB...

This causes a segfault with mariadb versions 10.3 and higher, if you call ping after disconnect. use Test::More; use DBI; say "please provide db name"; my $dbname = ; chomp...

I've been able to implement a workaround where disconnect is wrapped in a sub, and a flag set if the database version contains mariadb and version is 10.3 or higher,...

> Hello, just to note that `DBI:MariaDB` driver has fixed this problem and works fine with MariaDB 10.3. Hi Pali, no DBD::MariaDB does *not* fix the ping following disconnect segfault....

> @hashbangperl if there is still segfault with DBD::MariaDB please report it to our project https://github.com/gooddata/DBD-MariaDB/issues and we look at it... but it is strange as I was testing specially...

I've managed to trigger a segfault inside gdb with mysql dbd against mariadb, using the test above. I was working the machine hard, as it seems to happen when mariadb...

added PR with extra tests, which should fail if using mariadb 10.3 or newer server that's under load. https://github.com/perl5-dbi/DBD-mysql/pull/319