Date: 2012-03-01 14:42:20 +0100
From: Viktor Rosenfeld <<24hesk>>
To: SQL devs <>
Version: 11.7.7 (Dec2011-SP1) [obsolete]
CC: @njnes

Last updated: 2012-05-25 12:58:46 +0200

Comment 17036

Date: 2012-03-01 14:42:20 +0100
From: Viktor Rosenfeld <<24hesk>>

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.56 Safari/535.11
Build Identifier:

mserver5 terminates with a segmentation fault when executing the attached query. The error occurs even if the required tables are empty or if one requests a MAL plan with explain. The segfault occurs in bin_find_column at rel_bin.c:98. A backtrace is attached. There is no assertion when compiled with --enable-assert.

Reproducible: Always

Steps to Reproduce:

1. run mserver5, connect with mclient
2. create tables using create-schema.sql
3. run the query in test-query.sql

Actual Results:

MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = SELECT
count(*)
FROM
(
SELECT DISTINCT
node1.id AS id1, node2.id AS id2, node1.toplevel_corpus
FROM
node AS node1, rank AS rank1, component AS component1,
node AS node2, rank AS rank2, component AS component2
WHERE
component1.id = component2.id AND
component1.name IS NULL AND
component1.type = 'd' AND
component2.name IS NULL AND
component2.type = 'd' AND
rank1.component_ref = component1.id AND
rank1.node_ref = node1.id AND
rank1.pre = rank2.parent AND
rank2.component_ref = component2.id AND
rank2.node_ref = node2.id
) AS solutions;
ERROR = !Connection terminated

Expected Results:

+------+
| L6 |
+======+
| 0 |
+------+
1 tuple

The query returns the expected result, if the predicate

   component1.id = component2.id

or, alternatively, if one removes the OTHER predicates on component:

   component1.name IS NULL AND
   component1.type = 'd' AND
   component2.name IS NULL AND
   component2.type = 'd' AND

There is no output in merovingian.log.

$ mserver5 --version
MonetDB 5 server v11.7.7 "Dec2011-SP1" (64-bit, 64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 252.4GiB available memory, 24 available cpu cores
Libraries:
libpcre: 7.9 2009-04-11 (compiled with 7.9)
openssl: OpenSSL 0.9.8k 25 Mar 2009 (compiled with OpenSSL 0.9.8k 25 Mar 2009)
libxml2: 2.7.3 (compiled with 2.7.3)
Compiled by: rosenfel@moos (x86_64-unknown-linux-gnu)
Compilation: gcc -g
Linking : /usr/x86_64-suse-linux/bin/ld -m elf_x86_64

Comment 17037

Date: 2012-03-01 14:44:19 +0100
From: Viktor Rosenfeld <<24hesk>>

Created attachment 100
SQL to create required schema

Attached file: create-schema.sql (text/plain, 1643 bytes)
Description: SQL to create required schema

Comment 17038

Date: 2012-03-01 14:44:52 +0100
From: Viktor Rosenfeld <<24hesk>>

Created attachment 101
test query causing mserver5 to crash

Attached file: test-query.sql (text/plain, 643 bytes)
Description: test query causing mserver5 to crash

Comment 17039

Date: 2012-03-01 14:45:55 +0100
From: Viktor Rosenfeld <<24hesk>>

Created attachment 102
Backtrace of the crash

Attached file: backtrace (text/plain, 2580 bytes)
Description: Backtrace of the crash

Comment 17066

Date: 2012-03-13 10:15:15 +0100
From: @sjoerdmullender

A crash of mserver5 is unlikely to be a problem with monetdbd, so changing the product.

Comment 17067

Date: 2012-03-13 10:22:53 +0100
From: @sjoerdmullender

Changeset 2fb290ca2b74 made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2fb290ca2b74

Changeset description:

Added test for bug #3046.
The server does indeed crash.

Comment 17188

Date: 2012-04-27 14:24:27 +0200
From: @njnes

has been fixed by recent changes, in the join handling/relational to binary conversion.