MySQL Bugs: #99919: mysqladmin segmentation fault

Bug #99919	mysqladmin segmentation fault
Submitted:	17 Jun 2020 16:29	Modified:	17 Aug 2020 12:12
Reporter:	Craig Swanson	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S2 (Serious)
Version:	mysql-community-client-8.0.20-1.el7.x86_	OS:	CentOS (7.8.2003)
Assigned to:		CPU Architecture:	x86

Description:
mysql cli client segfaults on exit.  

gdb output:

# gdb /usr/bin/mysqladmin
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-119.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/mysqladmin...done.
(gdb) run -p status
Starting program: /usr/bin/mysqladmin -p status
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Enter password: 
Uptime: 1561  Threads: 2  Questions: 6  Slow queries: 0  Opens: 84  Flush tables: 3  Open tables: 35  Queries per second avg: 0.003

Program received signal SIGSEGV, Segmentation fault.
0x000000000042c517 in charset_uninit ()
    at /export/home2/pb2/build/sb_1-38523192-1585231255.58/rpm/BUILD/mysql-8.0.20/mysql-8.0.20/mysys/charset.cc:925
925	/export/home2/pb2/build/sb_1-38523192-1585231255.58/rpm/BUILD/mysql-8.0.20/mysql-8.0.20/mysys/charset.cc: No such file or directory.
Missing separate debuginfos, use: debuginfo-install mysql-community-client-8.0.20-1.el7.x86_64

---

Installed packages:mysql-community-server-8.0.20-1.el7.x86_64
mysql-community-client-8.0.20-1.el7.x86_64
mysql-community-common-8.0.20-1.el7.x86_64
mysql-community-devel-8.0.20-1.el7.x86_64
mysql80-community-release-el7-3.noarch
mysql-community-libs-8.0.20-1.el7.x86_64
mysql-community-libs-compat-8.0.20-1.el7.x86_64

How to repeat:
mysql -p or mysqladmin -p status 
segmentation fault on exit from the shell.

Suggested fix:
Looks like there may be references to RPM build folders.

Hi Mr. Swanson,

Thank you for your bug report.

However, I was not able to repeat your report. We can not verify the bug unless we are able to repeat it.

What commands have you run exactly when the crash happened. Also, please use downloads from our dev.mysql.com site and not from Linux distributor.

Last, but not least, let us know what configuration variables have you used, that are relevant for the operation of our command line clients.

Repo: we are using the mysql80-community repo.

I'll check the variables for something that may be referencing an external (broken) library. 

Thank you

We will be waiting on your feedback.

Also, please just confirm that you are using a binary package from our dev.mysql.com site and not from your Linux distro repository.

We are using binary rpms from the mysql80-community repo.

The gdb output references mysys/charset.cc.
This may give us a clue to what is going on.

New information:
We are using the full-text indexing collation as recommended here:
https://dev.mysql.com/doc/refman/8.0/en/full-text-adding-collation.html

The issue seems to be isolated to using the full-text indexing collation with mysql-community-client >= 8.0.20.

Steps to reproduce:

Add the collation for full-text indexing per the MySQL doc
upgrade to mysql-community 8.0.20 (also confirmed on 8.0.21-1.el7)
Restart mysqld 

Result: 
mysql, mysqladmin client utilities segfault on exit.

$ mysqladmin -p status
Enter password: 
Uptime: 18  Threads: 2  Questions: 2  Slow queries: 0  Opens: 84  Flush tables: 3  Open tables: 35  Queries per second avg: 0.111
Segmentation fault

Workaround:

downgrade to mysql-community-client-8.0.19

Hi Mr. Swanson,

Thank you for your comment.

However, we have already upgraded several times from 8.0.19 to 8.0.20 with full-text indices and had no problems, what so ever. 

Hence, we need a fully described, up to the last detail, repeatable test case, so that it could we could verify it and then work on it.

Also, since 8.0.21 is out, please check whether upgrade from 8.0.19 to 8.0.21 works well. In case it works well, then this is not a bug.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".