MySQL Bugs: #50345: Mysqld received signal 11

Bug #50345	Mysqld received signal 11
Submitted:	14 Jan 2010 18:52	Modified:	29 Mar 2011 19:01
Reporter:	Roberto Spadim (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.60	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	qc, Signal 11

Description:
hello my production server was restarted, i got this error on mysql log:

100114 15:20:21 - 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=1048576000
read_buffer_size=4190208
max_used_connections=95
max_connections=100
threads_connected=63
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1842799 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x2aaab01415c0
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=0x4179c0e0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
Stack trace seems successful - bottom reached
Please read http://dev.mysql.com/doc/mysql/en/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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x10b1a00 = INSERT HIGH_PRIORITY INTO est_mov (unidade_id,lote_tipo,lote_spa,item_id,item_id_red,mov_id,oe_tipo,oe,oe_seq,lote,lote_data,lote_sif_data,lote_sif,estoque_entrada_un,estoque_entrada_org,estoque_entrada_org_red,estoque_entrada_mapa,estoque_entrada_mapa_red,estoque_entrada_pess_tipo,estoque_entrada_pess_id,estoque_entrada_propriedade,estoque_entrada_proprietario_tipo,estoque_entrada_proprietario_id,estoque_saida_un,estoque_saida_org,estoque_saida_org_red,estoque_saida_mapa,estoque_saida_mapa_red,estoque_saida_pess_tipo,estoque_saida_pess_id,estoque_saida_propriedade,estoque_saida_proprietario_tipo,estoque_saida_proprietario_id,quant,pecas,pbruto,pliq,vbruto,vliq,quant_real,pecas_real,pbruto_real,pliq_real,vbruto_real,vliq_real,data_etiqueta,data_producao,data_processamento,data_validade,data_estoque,data_estoque_origem,data_estoque_destino,cfop_id,cfop_id_red,valor_bruto_total,valor_liq_total,custo,custo_medio_anterior,custo_medio_apos,quant_mov_un,rastreabilidade_interna,rastreabilidade_externa,rastreabilidad
thd->thread_id=20640
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
100114 15:20:21  mysqld restarted

any idea?? thanks

How to repeat:
i don't know

Suggested fix:
???

Thank you for the problem report. Please, send your my.cnf file content and the results of SHOW CREATE TABLE and SHOW TABLE STATUS for that est_mov table.

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

Thank you for the feedback.

I was not able to repeat described behavior with test data. Please try current version 5.0.91 and if problem still exists generate core file in time when mysqld crashes.

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

work with 5.5 thanks