Debug build Assertion from test: DBUG_ASSERT(!(table->key_info[active_index].flags & HA_UNIQUE_HASH)); connect.general

connect.general                          w12 [ fail ]

        Test ended at 2024-10-27 05:57:15

CURRENT_TEST: connect.general

mysqltest: At line 30: query 'DELETE FROM numbers WHERE n = 1' failed with wrong errno <Unknown> (2013): 'Lost connection to server during query', instead of ER_GET_ERRMSG (1296)...

The result from queries just before the failure was:

< snip >

INSERT INTO t1 VALUES (10);

SELECT * FROM t1;

a

10

ALTER TABLE t1 TABLE_TYPE=NON_EXISTING;

ERROR HY000: Unsupported table type NON_EXISTING

SELECT * FROM t1;

a

10

DROP TABLE t1;

#

# MDEV-23626: CONNECT VIR tables return inconsistent error for UPDATE

#

CREATE TABLE numbers

ENGINE=CONNECT,

TABLE_TYPE=VIR,

BLOCK_SIZE=3;

TRUNCATE TABLE numbers;

ERROR HY000: Got error 174 'Virtual tables are read only' from CONNECT

DELETE FROM numbers WHERE n = 1;

More results from queries before failure can be found in /home/buildbot/amd64-ubuntu-2004-debug/build/mysql-test/var/12/log/general.log

Server [mysqld.1 - pid: 94799, winpid: 94799, exit: 256] failed during test run

Server log from this test:

----------SERVER LOG START-----------

OpenTable: Virtual tables are read only

OpenTable: Virtual tables are read only

mariadbd: /home/buildbot/amd64-ubuntu-2004-debug/build/sql/handler.cc:3756: int handler::ha_index_init(uint, bool): Assertion `!(table->key_info[active_index].flags & 262144U)' failed.

241027  5:57:09 [ERROR] mysqld got signal 6 ;

Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed, 

something is definitely wrong and this may fail.

Server version: 11.2.6-MariaDB-debug-log source revision: 7926b1a5dd66d7ccd604bc8037e3eebb0cb414f7

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=1

max_threads=153

thread_count=1

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63998 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f6830000db8

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

stack_bottom = 0x7f6846f48c58 thread_stack 0x49000

mysys/stacktrace.c:215(my_print_stacktrace)[0x5612cc1cedb4]

sql/signal_handler.cc:247(handle_fatal_signal)[0x5612cb95261a]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7f685369a420]

/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f685318300b]

/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f6853162859]

/lib/x86_64-linux-gnu/libc.so.6(+0x22729)[0x7f6853162729]

/lib/x86_64-linux-gnu/libc.so.6(+0x33fd6)[0x7f6853173fd6]

sql/handler.cc:3758(handler::ha_index_init(unsigned int, bool))[0x5612cb95e3ce]

sql/opt_range.cc:13190(QUICK_RANGE_SELECT::reset())[0x5612cb431627]

sql/sql_delete.cc:693(Sql_cmd_delete::delete_from_single_table(THD*))[0x5612cb516d39]

sql/sql_delete.cc:1827(Sql_cmd_delete::execute_inner(THD*))[0x5612cb51aaff]

sql/sql_select.cc:34272(Sql_cmd_dml::execute(THD*))[0x5612cb632981]

sql/sql_parse.cc:4433(mysql_execute_command(THD*, bool))[0x5612cb57d2f3]

sql/sql_parse.cc:7938(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x5612cb588368]

sql/sql_parse.cc:1896(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x5612cb575bcb]

sql/sql_parse.cc:1407(do_command(THD*, bool))[0x5612cb574754]

sql/sql_connect.cc:1439(do_handle_one_connection(CONNECT*, bool))[0x5612cb74a79e]

sql/sql_connect.cc:1345(handle_one_connection)[0x5612cb74a520]

perfschema/pfs.cc:2203(pfs_spawn_thread)[0x5612cbc44403]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609)[0x7f685368e609]

/lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7f685325f353]

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0x7f6830015700): DELETE FROM numbers WHERE n = 1

Connection ID (thread ID): 51

Status: NOT_KILLED