Fixed broken mroonga_default_parser or mroonga_log_file variable

[samitani]

after SET GLOBAL same as before value, variables is broken.

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.5.36 MySQL Community Server (GPL)

Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show global variables like 'mroonga_default_parser';
+------------------------+-------------+
| Variable_name          | Value       |
+------------------------+-------------+
| mroonga_default_parser | TokenBigram |
+------------------------+-------------+
1 row in set (0.00 sec)

mysql> set global mroonga_default_parser=TokenBigram;
Query OK, 0 rows affected (0.00 sec)

mysql> show global variables like 'mroonga_default_parser';
+------------------------+------------------+
| Variable_name          | Value            |
+------------------------+------------------+
| mroonga_default_parser | /tmp/#sql_5fbd_0 |
+------------------------+------------------+
1 row in set (0.00 sec)

And also, crashed during shutdown.

Version: '5.5.36'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
140419 17:48:42 [Note] /usr/sbin/mysqld: Normal shutdown

140419 17:48:42 [Note] Event Scheduler: Purging the queue. 0 events
140419 17:48:42  InnoDB: Starting shutdown...
140419 17:48:43  InnoDB: Shutdown completed; log sequence number 1595675
08:48:43 UTC - 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=8388608
read_buffer_size=131072
max_used_connections=1
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 = 338511 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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a6125]
/usr/sbin/mysqld(handle_fatal_signal+0x403)[0x673b23]
/lib64/libpthread.so.0(+0xf710)[0x7f44776e8710]
/lib64/libc.so.6(+0x7878a)[0x7f44768f578a]
/usr/sbin/mysqld(free_root+0x11a)[0x79b97a]
/usr/sbin/mysqld[0x587083]
/usr/sbin/mysqld[0x5872e1]
/usr/sbin/mysqld(_Z15plugin_shutdownv+0x205)[0x587a75]
/usr/sbin/mysqld[0x5044f7]
/usr/sbin/mysqld(_Z10unireg_endv+0xe)[0x5047de]
/usr/sbin/mysqld[0x507f25]
/usr/sbin/mysqld(kill_server_thread+0x10)[0x508020]
/lib64/libpthread.so.0(+0x79d1)[0x7f44776e09d1]
/lib64/libc.so.6(clone+0x6d)[0x7f4476965b6d]
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.
140419 17:48:43 mysqld_safe Number of processes running now: 0
140419 17:48:43 mysqld_safe mysqld restarted

[kou]

Thanks!!!
I've merged your pull request and added tests for the cases!