Bug #57796 | mysqld segfaults, 'alter table' featured in backtrace | ||
---|---|---|---|
Submitted: | 28 Oct 2010 9:47 | Modified: | 24 Jul 2015 18:45 |
Reporter: | Matthew Bloch | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: GIS | Severity: | S1 (Critical) |
Version: | 5.1.51-linux-x86_64-glibc23 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | crash |
[28 Oct 2010 9:47]
Matthew Bloch
[28 Oct 2010 10:02]
MySQL Verification Team
Hi Matthew, can you please send output of SHOW CREATE TABLE shopper_postcode2;
[28 Oct 2010 10:39]
Matthew Bloch
Sent privately. Also NB that was from the current live copy of the database, not the one that crashed - as I said we don't have that data any more as we needed to redeploy quickly.
[16 Nov 2010 21:23]
Sveta Smirnova
Thank you for the feedback. I can not repeat the problem with test data. Looks like more information from your side needed. Please keep core file and table *frm, *MYD and *MYI files if problem occurs next time. Please also check OS error log file in case if it was real memory shortage at crash time.
[17 Dec 2010 0:00]
Bugs System
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".
[24 Jun 2015 18:05]
Tianzhou Chen
We also notice the same crash on 5.6.24 on linux Registers at time of signal: UNKNOWN: 18446744073709551615(0x7fa9b363e680(), 0x7fa9b363e680(), 0x0(), 0x0(), 0x7fa9e3a1cdd8(\310{\301\376@\201\301\376\010\201\301\376\270\200\301\376H\200\301\376\330\177\301\3760\177\301\376@\201\301\376\340~\301\376h~\301\376\270}\301\376\320|\301\376x|\301\376\030|\301\376\350{\301\376O\202\301\376\314\214\301\376\234\214\301\376,\214\301\376\\\213\301\376l\212\301\376\274\210\301\376\314\214\301\376\\\210\301\376|\207\301\376\274\205\301\376\324\203\301\376\014\203\301\376\\\202\301\376\014\202\301\376@\217\301\376X\225\301\376\030\225\301\376\240\224\301\376\360\223\301\3768\223\301\376), 0x7fa9b363f518(\223\024\303\246=\305\275R\223\024\303\246=\305\275R)) at eip 0x7fa9e2638993 (48 8b 55 98 c7 40 08 01) with eax 0 and base pointer 0x7fa9b363eb70 Stacktrace rtree_split_page(0x7fa9e2638993) rtree_add_key(0x7fa9e2632fc1) rtree_insert_req(0x7fa9e262dc2b) rtree_insert_level(0x7fa9e262dca6) rtree_insert(0x7fa9e262e314) mi_write(0x7fa9e2630abb) handler::ha_write_row(unsigned char*)(0x7fa9e2545160) write_record(THD*, TABLE*, COPY_INFO*, COPY_INFO*)(0x7fa9e23927c5) mysql_insert(THD*, TABLE_LIST*, List<Item>&, List<List<Item> >&, List<Item>&, List<Item>&, enum_duplicates, bool)(0x7fa9e2395c7d) mysql_execute_command(THD*)(0x7fa9e236c567) mysql_parse(THD*, char*, unsigned int, Parser_state*)(0x7fa9e236f6c8) dispatch_command(enum_server_command, THD*, char*, unsigned int)(0x7fa9e2371f27) do_handle_one_connection(THD*)(0x7fa9e23b2fd6) handle_one_connection(0x7fa9e23b2ff9) start_thread(0x7fa9e0dcb800) __clone(0x7fa9e08262ed)
[24 Jun 2015 18:45]
MySQL Verification Team
Hi, kindly try the newer versions of MySQL. I believe it would solve your issue. If not, let us know here. Referring to this in particular (based on stack trace of crash). ---------- Noted in 5.5.44, 5.6.25, 5.7.8, 5.8.0 changelogs. Loading corrupt spatial data into a MyISAM table could cause the server to exit during index building. ----------
[25 Jul 2015 1:00]
Bugs System
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".