Strange behaviour (bug ?) when closing MySQL.

[Fournier Jocelyn [Presence-PC]]

Hi,

I just experienced a strange bug in MySQL 3.23.39 I couldn't explain (and couldn't 
reproduce, it's why I post it on this list ;))
I misconfigured my my.cnf, so MySQL didn't found the host.frm.

The strange behaviour is just after the normal shutdown of mysql :

010717 00:01:19  mysqld started
010717  0:01:19  /var/lib/mysql/libexec/mysqld: Can't find file: './mysql/host.frm' 
(errno: 13)
010717  0:01:19  /var/lib/mysql/libexec/mysqld: Normal shutdown

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 agaist 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=268431360
record_buffer=8384512
sort_buffer=8388600
max_used_connections=0
max_connections=1000
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 4059220 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

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...
Cannot determine thread, fp=0xbf5ff638, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x806add4
0x810fdd8
0x806a2b7
0x806de2b
0x810d70e
0x8143b5a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow 
instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
Fatal signal 11 while backtracing
010717 00:01:19  mysqld ended

I retried several times to reproduce the bug, no way :(
The server is perfectly stable and was running for days MySQL without a glitch, it's 
why I don't think the hardware could be involved in this issue.

Do you have any idea of how it could have been happened ?

Thank you,

Jocelyn Fournier
Presence-PC