[MXS-3873] Crash in qc_sqlite Created: 2021-11-12  Updated: 2021-12-14  Resolved: 2021-11-15

Status: Closed
Project: MariaDB MaxScale
Component/s: qc_sqlite
Affects Version/s: 2.4.18
Fix Version/s: 2.4.19

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MXS-3585 query classifier crashes after upgrad... Closed

 Description   

2021-11-10 15:08:47   alert  : (62432) 
  /usr/lib64/maxscale/libqc_sqlite.so(+0x799b6): _build/sqlite-bld-3110100/sqlite3.c:132756
  /usr/lib64/maxscale/libqc_sqlite.so(+0x7d236): _build/sqlite-bld-3110100/sqlite3.c:135975
  /usr/lib64/maxscale/libqc_sqlite.so(+0x7d56d): _build/sqlite-bld-3110100/sqlite3.c:110381
  /usr/lib64/maxscale/libqc_sqlite.so(+0x7d8f9): _build/sqlite-bld-3110100/sqlite3.c:110480
  /usr/lib64/maxscale/libqc_sqlite.so(+0x7d987): _build/sqlite-bld-3110100/sqlite3.c:110546
  /usr/lib64/maxscale/libqc_sqlite.so(+0xb90b): query_classifier/qc_sqlite/qc_sqlite.cc:3664
  /usr/lib64/maxscale/libqc_sqlite.so(+0x16396): query_classifier/qc_sqlite/qc_sqlite.cc:3836
  /usr/lib64/maxscale/libqc_sqlite.so(+0x105aa): query_classifier/qc_sqlite/qc_sqlite.cc:5032
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_Z16qc_get_type_maskP5GWBUF+0x4b): /opt/rh/devtoolset-7/root/usr/include/c++/7/bits/basic_string.h:3295
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN8maxscale15QueryClassifier17update_route_infoENS0_16current_target_tEP5GWBUF+0x256): server/core/queryclassifier.cc:1039
  /usr/lib64/maxscale/libreadwritesplit.so(_ZN14RWSplitSession10routeQueryEP5GWBUF+0x23f): server/modules/routing/readwritesplit/rwsplitsession.cc:146
  /usr/lib64/maxscale/libreadwritesplit.so(_ZN8maxscale6RouterI7RWSplit14RWSplitSessionE10routeQueryEP10mxs_routerP18mxs_router_sessionP5GWBUF+0x21): include/maxscale/router.hh:452
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_Z19session_route_queryP11MXS_SESSIONP5GWBUF+0x18): server/core/session.cc:901
  /usr/lib64/maxscale/libmariadbclient.so(+0x6755): server/modules/protocol/MySQL/mariadbclient/mysql_client.cc:1995
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0xa19f2): server/core/dcb.cc:2706
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0xa1a61): server/core/dcb.cc:2758
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x196): maxutils/maxbase/src/worker.cc:858
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x53): maxutils/maxbase/src/worker.cc:559
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x1b951f): thread48.o:?
  /lib64/libpthread.so.0(+0x7e65): pthread_create.c:?
  /lib64/libc.so.6(clone+0x6d): ??:?



 Comments   
Comment by markus makela [ 2021-11-12 ]

Here's a SQL statement that reproduces it:

DELETE x FROM x JOIN (SELECT 1) y ON x.id = y.id;

Looks like it's the multi-table syntax that causes it.

Comment by markus makela [ 2021-11-15 ]

This seems to be a duplicate of MXS-3585 which was only found in 2.5. Cherry-picking the fix to 2.4 should solve it.

Generated at Thu Feb 08 04:24:34 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.