Description:
UPDATE rastreosat.gps021_programacion_equipo SET gps021_activo = 0 WHERE gps019_id_definicion_evento = 13 AND gps008_id_movil = 792
CPU Info
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 11
model name : Intel(R) Pentium(R) III CPU family 1400MHz
stepping : 1
cpu MHz : 1396.821
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 2793.78
1G of RAM
061006 16:42:35 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.24a-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
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=34
max_connections=256
threads_connected=34
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 654334 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0xab8cd80
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=0x82a442ac, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x817ec70
0x9c2898
0x29
0x82317d5
0x8227610
0x8227413
0x821b110
0x821ab98
0x8221197
0x81e8a98
0x819576b
0x81e7740
0x81e6479
0x81941c3
0x8192ccd
0x819223f
0x9bc371
0x80bffe
New value of fp=(nil) failed sanity check, terminating stack trace!
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 0xab90358 = UPDATE rastreosat.gps021_programacion_equipo SET gps021_activo = 1 WHERE gps019_id_definicion_evento = 7 AND gps008_id_movil = 792
thd->thread_id=45
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.
How to repeat:
The stack trace
0x817ec70 get_schema_views_record__FP3THDP13st_table_listP8st_tablebPCcT4 + 596
0x9c2898 (?)
0x29 (?)
0x82317d5 btr_search_update_hash_on_delete + 941
0x8227610 btr_estimate_n_rows_in_range + 544
0x8227413 btr_estimate_n_rows_in_range + 35
0x821b110 btr_validate_level + 596
0x821ab98 btr_validate_report1 + 184
0x8221197 btr_cur_open_at_rnd_pos + 1091
0x81e8a98 ibuf_get_volume_buffered + 940
0x819576b show_master_info__FP3THDP14st_master_info + 4675
0x81e7740 ibuf_get_merge_page_nos + 628
0x81e6479 ibuf_entry_build + 577
0x81941c3 init_master_info__FP14st_master_infoPCcT1bi + 1411
0x8192ccd init_relay_log_info__FP17st_relay_log_infoPCc + 349
0x819223f get_master_version_and_clock__FP8st_mysqlP14st_master_info + 219
0x9bc371 (?)
0x80bffe (?)
0x817ec70 get_schema_views_record__FP3THDP13st_table_listP8st_tablebPCcT4 + 596
0x9c2898 (?)
0x29 (?)
0x82317d5 btr_search_update_hash_on_delete + 941
0x8227610 btr_estimate_n_rows_in_range + 544
0x8227413 btr_estimate_n_rows_in_range + 35
0x821b110 btr_validate_level + 596
0x821ab98 btr_validate_report1 + 184
0x8221197 btr_cur_open_at_rnd_pos + 1091
0x81e8a98 ibuf_get_volume_buffered + 940
0x819576b show_master_info__FP3THDP14st_master_info + 4675
0x81e7740 ibuf_get_merge_page_nos + 628
0x81e6479 ibuf_entry_build + 577
0x81941c3 init_master_info__FP14st_master_infoPCcT1bi + 1411
