MySQL Bugs: #10033: Not routine crashing on 4.1.10a and 4.1.11

Bug #10033	Not routine crashing on 4.1.10a and 4.1.11
Submitted:	20 Apr 2005 15:27	Modified:	23 May 2005 1:19
Reporter:	Liber Chen	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.1.11	OS:	FreeBSD (FreeBSD 5.3 Release)
Assigned to:		CPU Architecture:	Any

Description:
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=134217728
read_buffer_size=1044480
max_used_connections=69
max_connections=100
threads_connected=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 335471 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
----
4.1.9 is working well,
and it occur after I upgrade to 4.1.10a.
And still happened after I upgrade to 4.1.11

Not routine, can't forecast...

How to repeat:
No method to repeat, but it will be crash cyclically.

Suggested fix:
Nothing so far.

Are you using binaries provided by MySQL or a ports build?

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".

I used source build.
And I have used linuxthread.