bug: debug version run mtr, mysqld --bootstrap cause crash

[davidshiz]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Please confirm if bug report does NOT exists already ?

• I confirm there is no existing issue for this

Describe the problem

[root@stonedb-test mysql-test]# ./mysql-test-run.pl --suite=tianmu aggregate.test
Logging: ./mysql-test-run.pl  --suite=tianmu aggregate.test
MySQL Version 5.7.36
Checking supported features...
 - SSL connections supported
 - binaries are debug compiled
Collecting tests...
Checking leftover processes...
Removing old var directory...
Creating var directory '/stonedb57/install/mysql-test/var'...
Installing system database...
mysql-test-run: *** ERROR: Error executing mysqld --bootstrap

/stonedb57/install/bin/mysqld --no-defaults --log-syslog=0 --bootstrap --basedir=/ll --datadir=/stonedb57/install/mysql-test/var/install.db --loose-skip-ndbcluster db57/install/mysql-test/var/tmp/ --secure-file-priv=/stonedb57/install/mysql-test/g-file-size=5M --core-file --innodb_autoextend_increment=8 --innodb_buffer_pool_sisages-dir=/stonedb57/install/share/ --character-sets-dir=/stonedb57/install/share/e-auto_generate_certs=OFF --loose-sha256_password_auto_generate_rsa_keys=OFF
2023-06-25T08:31:03.204814Z 0 [Warning] --bootstrap is deprecated. Please considerlize instead
08:31:04 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68262 K  byt
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/stonedb57/install/bin/mysqld(my_print_stacktrace+0x47)[0x3189561]
/stonedb57/install/bin/mysqld(handle_fatal_signal+0x72d)[0x1d796bb]
/lib64/libpthread.so.0(+0xf630)[0x7fa7d936d630]
/lib64/libc.so.6(gsignal+0x37)[0x7fa7d6d68387]
/lib64/libc.so.6(abort+0x148)[0x7fa7d6d69a78]
/stonedb57/install/bin/mysqld[0x1d466c2]
/stonedb57/install/bin/mysqld(__gxx_personality_v0+0xb6)[0x462e5b6]
/lib64/libgcc_s.so.1(+0xf9f4)[0x7fa7d69499f4]
/lib64/libgcc_s.so.1(_Unwind_ForcedUnwind+0x64)[0x7fa7d6949d44]
/lib64/libpthread.so.0(__pthread_unwind+0x42)[0x7fa7d936c362]
/lib64/libpthread.so.0(+0x8ef7)[0x7fa7d9366ef7]
/stonedb57/install/bin/mysqld[0x319b4a3]
/stonedb57/install/bin/mysqld(signal_hand+0x80e)[0x1d4e110]
/stonedb57/install/bin/mysqld(pfs_spawn_thread+0x248)[0x3a41d25]
/lib64/libpthread.so.0(+0x7ea5)[0x7fa7d9365ea5]
/lib64/libc.so.6(clone+0x6d)[0x7fa7d6e30b0d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file

Expected behavior

No response

How To Reproduce

No response

Environment

[root@stonedb-test install.db]# /stonedb57/install/bin/mysqld --version
/stonedb57/install/bin/mysqld  Ver 5.7.36-StoneDB-v1.0.1.105b730 for Linux on x86_64 (build-)
build information as follow:
        Repository address: https://github.com/stoneatom/stonedb.git:stonedb-5.7-dev
        Branch name: stonedb-5.7-dev
        Last commit ID: 105b730
        Last commit time: Date:   Tue Jun 20 19:24:22 2023 +0800
        Build time: Date: Sun Jun 25 07:54:13 UTC 2023

Are you interested in submitting a PR to solve the problem?

• Yes, I will!