MacOS Crash when testing

Logging: /Users/huangweijun/Desktop/MariaDB/MariaDB_server/mysql-test/mariadb-test-run.pl  alias

VS config: 

vardir: /Users/huangweijun/Desktop/MariaDB/build/mysql-test/var

Checking leftover processes...

Removing old var directory...

Creating var directory '/Users/huangweijun/Desktop/MariaDB/build/mysql-test/var'...

Checking supported features...

MariaDB Version 11.1.0-MariaDB-debug

 - SSL connections supported

 - binaries are debug compiled

 - binaries built with wsrep patch

Collecting tests...

Installing system database...

mysql-test-run: *** ERROR: Error executing mariadbd --bootstrap

Could not install system database from /Users/huangweijun/Desktop/MariaDB/build/mysql-test/var/log/bootstrap.sql

The /Users/huangweijun/Desktop/MariaDB/build/mysql-test/var/log/bootstrap.log file contains:

/Users/huangweijun/Desktop/MariaDB/build/sql/mariadbd --no-defaults --disable-getopt-prefix-matching --bootstrap --basedir=/Users/huangweijun/Desktop/MariaDB/MariaDB_server --datadir=/Users/huangweijun/Desktop/MariaDB/build/mysql-test/var/install.db --plugin-dir=/Users/huangweijun/Desktop/MariaDB/build/mysql-test/var/plugins --default-storage-engine=myisam --loose-skip-plugin-feedback --loose-skip-plugin-innodb --loose-skip-plugin-innodb-buffer-page-lru --loose-skip-plugin-innodb-buffer-pool-stats --loose-skip-plugin-innodb-cmp --loose-skip-plugin-innodb-cmp-per-index --loose-skip-plugin-innodb-cmp-per-index-reset --loose-skip-plugin-innodb-cmp-reset --loose-skip-plugin-innodb-cmpmem --loose-skip-plugin-innodb-cmpmem-reset --loose-skip-plugin-innodb-ft-being-deleted --loose-skip-plugin-innodb-ft-config --loose-skip-plugin-innodb-ft-default-stopword --loose-skip-plugin-innodb-ft-deleted --loose-skip-plugin-innodb-ft-index-cache --loose-skip-plugin-innodb-ft-index-table --loose-skip-plugin-innodb-sys-columns --loose-skip-plugin-innodb-sys-fields --loose-skip-plugin-innodb-sys-foreign --loose-skip-plugin-innodb-sys-foreign-cols --loose-skip-plugin-innodb-sys-indexes --loose-skip-plugin-innodb-sys-tables --loose-skip-plugin-innodb-sys-tablespaces --loose-skip-plugin-innodb-sys-tablestats --loose-skip-plugin-innodb-sys-virtual --loose-skip-plugin-innodb-tablespaces-encryption --loose-skip-plugin-partition --loose-skip-plugin-sequence --loose-skip-plugin-thread-pool-groups --loose-skip-plugin-thread-pool-queues --loose-skip-plugin-thread-pool-stats --loose-skip-plugin-thread-pool-waits --loose-skip-plugin-unix-socket --loose-skip-plugin-user-variables --loose-skip-plugin-wsrep-provider --loose-innodb --loose-innodb-log-file-size=10M --disable-sync-frm --tmpdir=/Users/huangweijun/Desktop/MariaDB/build/mysql-test/var/tmp/ --core-file --console --character-set-server=latin1 --lc-messages-dir=/Users/huangweijun/Desktop/MariaDB/build/sql/share/ --character-sets-dir=/Users/huangweijun/Desktop/MariaDB/MariaDB_server/sql/share/charsets

2023-03-22 14:05:34 0 [Warning] Could not increase number of max_open_files to more than 1024 (request: 32190)

2023-03-22 14:05:34 0 [Warning] Changed limits: max_open_files: 1024  max_connections: 151 (was 151)  table_cache: 421 (was 2000)

2023-03-22 14:05:34 0 [Warning] Setting lower_case_table_names=2 because file system for /Users/huangweijun/Desktop/MariaDB/build/mysql-test/var/install.db/ is case insensitive

2023-03-22 14:05:34 0 [Note] Starting MariaDB 11.1.0-MariaDB-debug source revision bdcb2ae5097eb66b3e9a725890bb8d11283e678a as process 57646

2023-03-22 14:05:34 0 [Note] Plugin 'partition' is disabled.

2023-03-22 14:05:34 0 [Note] Plugin 'SEQUENCE' is disabled.

2023-03-22 14:05:34 0 [Note] InnoDB: The first data file './ibdata1' did not exist. A new tablespace will be created!

2023-03-22 14:05:34 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!

2023-03-22 14:05:34 0 [Note] InnoDB: Compressed tables use zlib 1.2.11

2023-03-22 14:05:34 0 [Note] InnoDB: Number of transaction pools: 1

2023-03-22 14:05:34 0 [Note] InnoDB: Using generic crc32 instructions

2023-03-22 14:05:34 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB

2023-03-22 14:05:34 0 [Note] InnoDB: Completed initialization of buffer pool

2023-03-22 14:05:34 0 [Note] InnoDB: Setting file './ibdata1' size to 12.000MiB. Physically writing the file full; Please wait ...

2023-03-22 14:05:34 0 [Note] InnoDB: File './ibdata1' size is now 12.000MiB.

2023-03-22 14:05:34 0 [Note] InnoDB: Data file .//undo001 did not exist: new to be created

2023-03-22 14:05:34 0 [Note] InnoDB: Setting file .//undo001 size to 10.000MiB

2023-03-22 14:05:34 0 [Note] InnoDB: Database physically writes the file full: wait...

2023-03-22 14:05:34 0 [Note] InnoDB: Data file .//undo002 did not exist: new to be created

2023-03-22 14:05:34 0 [Note] InnoDB: Setting file .//undo002 size to 10.000MiB

2023-03-22 14:05:34 0 [Note] InnoDB: Database physically writes the file full: wait...

2023-03-22 14:05:34 0 [Note] InnoDB: Data file .//undo003 did not exist: new to be created

2023-03-22 14:05:34 0 [Note] InnoDB: Setting file .//undo003 size to 10.000MiB

2023-03-22 14:05:34 0 [Note] InnoDB: Database physically writes the file full: wait...

safe_mutex: Got error: 22 (2) when doing a safe_mutex_wait on mutex at /Users/huangweijun/Desktop/MariaDB/MariaDB_server/storage/innobase/include/buf0dblwr.h, line 192

230322 14:05:34 [ERROR] 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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed, 

something is definitely wrong and this may fail.

Server version: 11.1.0-MariaDB-debug source revision: bdcb2ae5097eb66b3e9a725890bb8d11283e678a

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=0

max_threads=153

thread_count=0

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468175 K  bytes of memory

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 = 0x0 thread_stack 0x49000

Printing to addr2line failed

0   mariadbd                            0x00000001056a7d1c my_print_stacktrace + 64

0   mariadbd                            0x00000001046b9ac0 handle_fatal_signal + 1096

0   libsystem_platform.dylib            0x0000000182aeb4a4 _sigtramp + 56

0   libsystem_pthread.dylib             0x0000000182ad3ee0 pthread_kill + 288

0   libsystem_c.dylib                   0x0000000182a0e340 abort + 168

0   mariadbd                            0x00000001056ae008 safe_cond_wait + 644

0   mariadbd                            0x000000010515c12c _ZN11buf_dblwr_t20wait_for_page_writesEv + 92

0   mariadbd                            0x0000000105161fd4 _ZL14buf_flush_waity + 428

0   mariadbd                            0x00000001051630d0 _Z14buf_flush_syncv + 188

0   mariadbd                            0x000000010556548c _Z9srv_startb + 5860

0   mariadbd                            0x00000001052cf1f4 _ZL11innodb_initPv + 1648

0   mariadbd                            0x00000001046bbbcc _Z24ha_initialize_handlertonP13st_plugin_int + 356

0   mariadbd                            0x0000000104af7228 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 872

0   mariadbd                            0x0000000104af69e8 _Z11plugin_initPiPPci + 3140

0   mariadbd                            0x00000001048d6ec8 _ZL22init_server_componentsv + 3752

0   mariadbd                            0x00000001048d332c _Z11mysqld_mainiPPc + 1632

0   mariadbd                            0x00000001045e1b8c main + 36

0   dyld                                0x000000010805908c start + 520

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains

information that should help you find out what is causing the crash.

Core pattern: /cores/core.%P