MySQL Bugs: #7546: "RESET MASTER" crashed MySQL-server 4.1.8

Bug #7546	"RESET MASTER" crashed MySQL-server 4.1.8
Submitted:	27 Dec 2004 14:07	Modified:	30 Jan 2005 11:42
Reporter:	Micke Moggia	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1.8	OS:	Linux (Red Hat Linux)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Did a "RESET MASTER" and the MySQL Server crashed severly. Have never seen this before. 
Didn't do anything else with the database except this command. Are running a large database (> 
20GB) with only innoDB-tables on a dedicated machine that only runs MySQL.

How to repeat:
"RESET MASTER"

From the error-log:

Version: '4.1.8-standard-log'  socket: '/tmp/mysql.sock'  port: 3306  Official MySQL-standard 
binary
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=8
read_buffer_size=4190208
max_used_connections=91
max_connections=600
threads_connected=15
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 6141595 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Number of processes running now: 0

Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://www.mysql.com/doc/en/Making_trace_files.html

Once you have generated a backtrace, please submit it to this bug
report and change the status back to 'Open'. Thank you for helping
us make our products better.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".