Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

invalid memory address or nil pointer dereference #33070

Closed
ChenPeng2013 opened this issue Mar 15, 2022 · 0 comments · Fixed by #33204
Closed

invalid memory address or nil pointer dereference #33070

ChenPeng2013 opened this issue Mar 15, 2022 · 0 comments · Fixed by #33204
Assignees
Labels
severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@ChenPeng2013
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)


use test;
drop table if exists UK_GCOL_STORED_17616;
CREATE TABLE `UK_GCOL_STORED_17616` (
  `COL102` bit(16) DEFAULT NULL,
  `COL103` bit(16) DEFAULT NULL,
  `COL1` bit(16) GENERATED ALWAYS AS (`COL102` % 10) STORED,
  `COL2` varchar(20) DEFAULT NULL,
  `COL4` datetime DEFAULT NULL,
  `COL3` bigint(20) DEFAULT NULL,
  `COL5` float DEFAULT NULL,
  UNIQUE KEY `UK_COL1` (`COL1`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin;
prepare stmt from 'select t1.col1, t2.col1 from UK_GCOL_STORED_17616 as t1 left join UK_GCOL_STORED_17616 as t2 on t1.col1 = t2.col1 where t1.col1 not in (?, ?, ?)';
set @a=-25654, @b=-27622, @c=-19088;
execute stmt using @a,@b,@c;

2. What did you expect to see? (Required)

3. What did you see instead (Required)


MySQL [test]> execute stmt using @a,@b,@c;
ERROR 1105 (HY000): runtime error: invalid memory address or nil pointer dereference

4. What is your TiDB version? (Required)

Release Version: v6.0.0-alpha-82-g7ca9aff
Edition: Community
Git Commit Hash: 7ca9affabb3e1ba05bb3a3b357c2bf491d9ed330
Git Branch: master
UTC Build Time: 2022-03-15 01:02:37
GoVersion: go1.17.6
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
@ChenPeng2013 ChenPeng2013 added type/bug The issue is confirmed as a bug. sig/planner SIG: Planner severity/moderate labels Mar 15, 2022
@Yisaer Yisaer self-assigned this Mar 17, 2022
@ti-chi-bot ti-chi-bot added may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.0 labels Mar 18, 2022
@Yisaer Yisaer removed may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. affects-6.0 labels Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants