[MDEV-4288] DDL: crash after uninitialized read in row_merge_buf_add Created: 2013-03-17  Updated: 2014-01-14  Resolved: 2014-01-14

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: sbester1 Assignee: Elena Stepanova
Resolution: Fixed Votes: 0
Labels: upstream
Environment:

Linux x64, Win x64


Issue Links:
Blocks
is blocked by MDEV-3932 5.6 merge Closed

 Description   

Version: '10.0.1-MariaDB' Source distribution
Conditional jump or move depends on uninitialised value(s)
at: row_merge_buf_add (row0merge.cc:398)
by: row_merge_read_clustered_index (row0merge.cc:269)
by: row_merge_build_indexes (row0merge.cc:2994)
by: ha_innobase::add_index (handler0alter.cc:1303)
by: mysql_alter_table (sql_table.cc:6958)
by: Alter_table_statement::execute (sql_alter.cc:106)
by: mysql_execute_command (sql_parse.cc:4834)
by: mysql_parse (sql_parse.cc:6124)
by: dispatch_command (sql_parse.cc:1266)
by: do_handle_one_connection (sql_connect.cc:1267)
by: handle_one_connection (sql_connect.cc:1181)
by: start_thread (pthread_create.c:309)

--source include/have_innodb.inc
--disable_abort_on_error
 
drop table if exists `i` ;
create table `i`(`t` char (3))engine=innodb row_format=compact default charset=latin1;
insert `i` values ('a') ;
alter table `i` add column `l` int,add column `j` int not null  ;
alter table `i` add fulltext index (`t`) ,add fulltext index (`t`) ;
alter table `i` add unique (`j`);



 Comments   
Comment by Elena Stepanova [ 2013-03-17 ]

Assertion failure on a debug build:

InnoDB: Assertion failure in thread 139798702454528 in file row0merge.cc line 1325
InnoDB: Failing assertion: n_cols == dict_table_get_n_cols(new_table)

Also reproducible on MySQL 5.6.5 (InnoDB from which MariaDB 10.0.1 includes), but not on 5.6.10, so hopefully it will be fixed automatically by the merge, along with other 5.6.5-InnoDB-specific bugs

Comment by Elena Stepanova [ 2013-05-27 ]

Since the upstream bug has apparently been fixed, and the fix is expected to make it to 10.0 with a merge, I'm reducing the priority.

Comment by Sergei Golubchik [ 2014-01-14 ]

Could you please test whether it was fixed?

Comment by Elena Stepanova [ 2014-01-14 ]

Fixed in 10.0.4

Generated at Thu Feb 08 06:55:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.