Limitations/Differences with a MariaDB Server Compiled for Debugging    A MariaDB server configured with --with-debug=full has the following differences from a normal MariaDB server: 
You can have maximum of 1000 tables locked at the same time in one statement. (Define MAX_LOCKS in mysys/thrlock.c). This is to detect loops in the used lists. 
You can have maximum of 1000 threads locking the same table. (Define MAX_THREADS in mysys/thrlock.c). This is to detect loops in the used lists. 
Deadlock detection of mutex will be suzanne50@example.com. If wrong mutex handling is found an error will be printed to the error log. (Define SAFE_MUTEX) 
Memory overrun/underrun and not freed memory will be reported to the error log (Define SAFEMALLOC) 
You can get a trace of what mysqld (and most other binaries) is doing by starting it with the --debug option. The trace is usually put in /tmp or C:\ 
    Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.  

    
{'path': 'public/docs/mariadb/limitationsdifferences-with-a-mariadb-server-compiled-for-debugging/index.html', 'source': 'DevDocs.IO'}