mariabackup crashes when called without parameters on Windows

201103 10:01:41 [ERROR] mysqld got exception 0xc0000005 ;

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: 10.5.6-MariaDB

key_buffer_size=0

read_buffer_size=131072

max_used_connections=0

max_threads=1

thread_count=0

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5337 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...

ucrtbase.dll!strcmp()

mariadb-backup.exe!get_defaults_options()[my_default.c:293]

mariadb-backup.exe!my_load_defaults()[my_default.c:419]

mariadb-backup.exe!load_defaults()[my_default.c:363]

mariadb-backup.exe!handle_options()[xtrabackup.cc:5907]

mariadb-backup.exe!main()[xtrabackup.cc:6122]

mariadb-backup.exe!__scrt_common_main_seh()[exe_common.inl:288]

KERNEL32.DLL!BaseThreadInitThunk()

ntdll.dll!RtlUserThreadStart()

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.

Writing a core file at D:\JiveX\mariaDB\bin\

Minidump written to D:\JiveX\mariaDB\bin\mariadb-backup.dmp