[MDEV-10705] Assertion `n < m_size' failed in Element_type& Bounds_checked_array<Element_type>::operator[](size_t) [with Element_type = Item*; size_t = long unsigned int] Created: 2016-08-30 Updated: 2018-04-18 Resolved: 2017-01-09 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Optimizer |
| Affects Version/s: | 5.5, 10.0, 10.1, 10.2 |
| Fix Version/s: | 5.5.55, 10.0.29, 10.1.21, 10.2.4 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Elena Stepanova | Assignee: | Igor Babaev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
|
| Comments |
| Comment by Alexander Barkov [ 2016-12-26 ] | |||
|
The problem was introduced by this change:
| |||
| Comment by Igor Babaev [ 2016-12-28 ] | |||
|
The problem with the submitted test case really appeared with my merge from the mysql code. Yet the bug itself existed before this merge. Here's what we have for 10.0 and most probably for the earlier versions: {no format}MariaDB [test]> SELECT 1 UNION ( SELECT 2 ORDER BY NULL, @a0 := 3, @a1 := 3, @a2 := 3, @a3 := 3, @a4 := 3, @a5 := 3, @a6 := 3, @a7 := 3, @a8 := 3, @a9 := 3, @a10 := 3 ); ERROR 2006 (HY000): MySQL server has gone away{no format} With this test case we have on the server side: {no format}Version: '10.0.29-MariaDB-debug' socket: '/tmp/mysql.sock' port: 3306 Source distribution [New Thread 0x7ffff7f8b710 (LWP 10381)] mysqld: /home/igor/maria-git/10.0/sql/sql_select.cc:21483: bool find_order_in_list(THD*, Item*, TABLE_LIST, ORDER*, List<Item>&, List<Item>&, bool): Assertion `all_fields.elements <= thd->lex->current_select->ref_pointer_array_size' failed. Thread 27 "mysqld" received signal SIGABRT, Aborted. [Switching to Thread 0x7ffff7f8b710 (LWP 10381)] 0x00007ffff62b39e5 in raise () from /lib64/libc.so.6{no format} | |||
| Comment by Igor Babaev [ 2016-12-29 ] | |||
|
This bug was introduced by the fix for bug mdev-5104 (in the commit 883af99e7dac91e3f258135a2053e6b8e3c05fc3). | |||
| Comment by Igor Babaev [ 2017-01-09 ] | |||
|
The fix for this bug was pushed into the 5.5 tree (actually this is a 5.3 bug). |