Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
1.4.3, 1.5.2
-
None
-
2020-8
Description
If you run test005.sh, it completes fine.
Run it again and you get segv.
The problem appears that ha_mcs::condStack ends up with a garbage entry.
The server reuses handlers, which are created for each table. If a query has a subquery that uses cond_push, it doesn't call cond_pop, leaving the cond on the stack. The next query that uses that handler, has a (now possibly deleted) pointer to a previous query's cond on the condStack.