[MDEV-21495] Conditional jump or move depends on uninitialised value in sel_arg_range_seq_next Created: 2020-01-15 Updated: 2020-05-26 Resolved: 2020-05-26 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Optimizer |
| Affects Version/s: | 10.1, 10.2, 10.3, 10.4, 10.5 |
| Fix Version/s: | 10.5.4, 10.1.46, 10.2.33, 10.3.24, 10.4.14 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Varun Gupta (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Reproducible with 10.4, 10.5. |
| Comments |
| Comment by Oleksandr Byelkin [ 2020-05-13 ] | |||||||||||
|
main.innodb_icp main.select_pkeycache main.column_compression_parts main.partition (at least in 10.5) | |||||||||||
| Comment by Varun Gupta (Inactive) [ 2020-05-25 ] | |||||||||||
|
A simple test case demonstrating the variable is initialized.
Somehow i don't see the problem in 10.1 or 10.2, but looks the problem is there too | |||||||||||
| Comment by Varun Gupta (Inactive) [ 2020-05-25 ] | |||||||||||
|
Debugging I put a breakpoint here
I see that max_key_parts is not initialised here and then we use max_key_parts when we walk over the ranges
and this is where we access the uninitialised value for max_key_parts. The fix would be to initialize max_key_parts in sel_arg_range_seq_init | |||||||||||
| Comment by Igor Babaev [ 2020-05-25 ] | |||||||||||
|
It's ok to push it 10.1 |