var() possibly not working in debug builds

[monetdb-team]

Date: 2015-04-19 14:23:31 +0200
From: sorear
To: MonetDB5 devs <>
Version: 11.19.7 (Oct2014-SP1)
CC: @mlkersten, @drstmane

Last updated: 2015-06-22 22:32:25 +0200

Comment 20815

Date: 2015-04-19 14:23:31 +0200
From: sorear

When I run "select * from var();" in a freshly started database, I get an immediate assertion failure:

2015-04-19 05:05:51 ERR gt[6067]: mserver5: ../../../../MonetDB-11.19.7/sql/backends/monet5/sql.c:1378: sql_variables: Assertion `v->vtype == 5' failed.

v->vtype is 4 (TYPE_bat) in this case; I guess this is because the sql_variables MAL op is declared to return a bat in the sql.mal, but the argument checking wants a pointer to int.

+------------------------------------------------------------------+
| mal |
+==================================================================+
| function user.s2_1{autoCommit=true}():void; |
| X_2:bat[:oid,:str] := sql.sql_variables(); |
| X_3 := sql.resultSet(1,1,X_2); |
| sql.rsColumn(X_3,".","name","varchar",1024,0,X_2); |
| X_11 := io.stdout(); |
| sql.exportResult(X_11,X_3); |
| end s2_1; |
| querylog.define("explain select * from var();","default_pipe") |
+------------------------------------------------------------------+

MonetDB 5 server v11.19.7 "Oct2014-SP1" (64-bit, 64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2014 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 1.8GiB available memory, 2 available cpu cores
Libraries:
libpcre: 7.8 2008-09-05 (compiled with 7.8)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e-fips 11 Feb 2013)
libxml2: 2.7.6 (compiled with 2.7.6)
Compiled by: REDACTED (x86_64-unknown-linux-gnu)
Compilation: gcc -g
Linking : /usr/bin/ld -m elf_x86_64

Comment 20877

Date: 2015-05-20 22:41:09 +0200
From: @mlkersten

The issue can not be reproduced on the default branch.
I consider it closed until further notice.

Comment 20878

Date: 2015-05-20 23:05:34 +0200
From: @drstmane

For the records:

The problem is reproducible as reported with Oct2014 and Oct2014-SP1,
but appears to be fixed as of Oct2014-SP2.

Please upgrade to the latest Oct2014-SP3 (or the upcoming Oct2014-SP4 once it will be released).