MySQL Bugs: #41773: Crash if mysqld --userroot

Bug #41773	Crash if mysqld --userroot
Submitted:	28 Dec 2008 22:47	Modified:	30 Jul 2009 12:24
Reporter:	Peter Gulutzan	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: General	Severity:	S3 (Non-critical)
Version:	6.1.0-alpha-debug, 6.0-falcon, 5.4	OS:	Linux
Assigned to:	Alexander Nozdrin	CPU Architecture:	Any
Tags:	regression

Description:
I start mysqld with --userroot (yes, I typed wrong).
Crash.

I label this a 'foreign key' problem because it
happens only with mysql-6.1-fk, mysql-6.0 is fine.

How to repeat:
/usr/local/mysql/libexec/mysqld --userroot  

With mysql-6.0 the result looks like:
"
linux:/home/pgulutzan/.bazaar/shared_repository_directory/mysql-6.0 # /usr/local/mysql/libexec/mysqld --userroot
081226 16:03:56 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

081226 16:03:56 [ERROR] Aborting

081226 16:03:56 [Note] /usr/local/mysql/libexec/mysqld: Shutdown complete
"

With mysql-6.1-fk the result looks like:
"
linux:/home/pgulutzan/.bazaar/shared_repository_directory/mysql-6.1-fk # /usr/local/mysql/libexec/mysqld --userroot
081226 16:15:52 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

081226 16:15:52 [ERROR] Aborting

081226 16:15:52 - mysqld got signal 11 ;
This could be because you hit a bug. ...

Happens in 6.0, too. I used mysql-6.0-falcon tree on my 64-bit Debian for testing:

root@lu0011:~# /usr/local/mysql/libexec/mysqld --userroot
081229  4:04:07 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

081229  4:04:07 [ERROR] Aborting

081229  4:04:07 - mysqld got signal 11 ;
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.
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.

key_buffer_size=0
read_buffer_size=2097152
max_used_connections=0
max_threads=512
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 = 2102584 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 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 = (nil) thread_stack 0x40000
/usr/local/mysql/libexec/mysqld(my_print_stacktrace+0x2e) [0xae6d5e]
/usr/local/mysql/libexec/mysqld(handle_segfault+0x336) [0x67e016]
/lib/libpthread.so.0 [0x7f6fe9110a80]
/usr/local/mysql/libexec/mysqld(delegates_destroy()+0x14) [0x81a544]
/usr/local/mysql/libexec/mysqld [0x67d32c]
/usr/local/mysql/libexec/mysqld(unireg_abort+0x31) [0x67f6e1]
/usr/local/mysql/libexec/mysqld(main+0x31a) [0x68304a]
/lib/libc.so.6(__libc_start_main+0xe6) [0x7f6fe7fd31a6]
/usr/local/mysql/libexec/mysqld(__gxx_personality_v0+0x269) [0x5ab3d9]
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.

Can not repeat in mysql-azalea:
------------------------------------------------------
(quad)[~/MySQL/bzr/00.builds/azalea]> ./sql/mysqld --userroot
090730 16:23:29 [ERROR] An old style --language value with language specific part detected: /mnt/raid/alik/MySQL/bzr/00.builds/azalea/sql/share/english/
090730 16:23:29 [ERROR] Use --lc-messages-dir without language specific part instead.
090730 16:23:29 [Note] Plugin 'FEDERATED' is disabled.
090730 16:23:29 [Note] Plugin 'ndbcluster' is disabled.
090730 16:23:29  InnoDB: Started; log sequence number 0 46409
090730 16:23:29 [ERROR] ./sql/mysqld: unknown option '--userroot'
090730 16:23:29 [ERROR] Aborting

090730 16:23:29  InnoDB: Starting shutdown...
090730 16:23:30  InnoDB: Shutdown completed; log sequence number 0 46409
090730 16:23:30 [Warning] Forcing shutdown of 2 plugins
090730 16:23:30 [Note] ./sql/mysqld: Shutdown complete
------------------------------------------------------

It's also fixed in mysql-6.1-fk, which is what matters.