mysql_upgrade from MySQL 5.0 crashes in DBUG_ASSERT
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
New
|
Undecided
|
Unassigned |
Bug Description
Trying to run mysql_upgrade from MySQL 5.0 to Mariadb 5.2 crashes
in DBUG_ASSERT()
Version: '5.2.5-
Assertion failed: next_chunk <= buff_end, file ..\..\sql\table.cc, line 998
110130 0:58:06 [ERROR] mysqld got exception 0x80000003 ;
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=0
read_buffer_
max_used_
max_threads=102
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x16850f38
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...
002CB9A3 mysqld.
00298DA9 mysqld.
0029D4D6 mysqld.
008A6847 mysqld.
0044A45E mysqld.
00449579 mysqld.
003ABBF2 mysqld.
003B4166 mysqld.
003B39EE mysqld.
003B1697 mysqld.
003B4DD8 mysqld.
003B5F54 mysqld.
003037A2 mysqld.
003B59A2 mysqld.
00400C8E mysqld.
004322BC mysqld.
0043AEE2 mysqld.
0042EA2A mysqld.
0042E274 mysqld.
0032C41B mysqld.
008D925D mysqld.
008AAD23 mysqld.
008AACB9 mysqld.
75A63677 kernel32.
77AC9D42 ntdll.dll!
77AC9D15 ntdll.dll!
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 16869E20=ALTER TABLE procs_priv
ENGINE=MyISAM,
CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin
thd->thread_id=4
thd->killed=
Subsequent attempt to start fails with the same assertion but in different code path:
thd: 0x1e28b000
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...
00CAB9A3 mysqld.
00C78DA9 mysqld.
00C7D4D6 mysqld.
01286847 mysqld.
00E2A45E mysqld.
00E29579 mysqld.
00D8BBF2 mysqld.
00D94166 mysqld.
00D939EE mysqld.
00D91697 mysqld.
00D9F13D mysqld.
00DCCFF5 mysqld.
00CAC869 mysqld.
00CAF841 mysqld.
0128AD23 mysqld.
0128ACB9 mysqld.
75A63677 kernel32.
77AC9D42 ntdll.dll!
77AC9D15 ntdll.dll!
Assertion seems to come from this code in table.cc
if (share- >mysql_ version >= 50110) STORAGE_ ENGINE >auto_partition ed= *next_chunk; ASSERT( next_chunk <= buff_end); <-- HERE
{
/* New auto_partitioned indicator introduced in 5.1.11 */
#ifdef WITH_PARTITION_
share-
#endif
next_chunk++;
DBUG_
}