Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sqlitelogictest crash in simple select query #6435

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

Sqlitelogictest crash in simple select query #6435

monetdb-team opened this issue Nov 30, 2020 · 0 comments
Labels

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2017-10-18 16:56:22 +0200
From: @PedroTadim
To: SQL devs <>
Version: -- development
CC: @njnes

Last updated: 2017-10-26 14:01:37 +0200

Comment 25759

Date: 2017-10-18 16:56:22 +0200
From: @PedroTadim

User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36
Build Identifier:

Mserver receives a SIGSEV while compiling a SELECT query

Reproducible: Always

Steps to Reproduce:

  1. CREATE TABLE tab0(pk INTEGER PRIMARY KEY, col0 INTEGER, col1 FLOAT, col2 TEXT, col3 INTEGER, col4 FLOAT, col5 TEXT);
  2. SELECT ALL * FROM tab0 cor0 WHERE - 62 NOT IN ( 9, - ( + + 67 ) ) AND - col0 * + 51 BETWEEN + 8 AND - - 95;

Actual Results:

A SIGSEGV in score_gbe function call.

Expected Results:

An empty result set.

The SIGSEV:

Thread 7 "mserver5" received signal SIGSEGV, Segmentation fault.
0x00007fffe8b25392 in score_gbe (sql=0x7fffb800ab40, rel=0x7fffb8071a70, e=0x7fffb8072650) at rel_optimizer.c:4841
4841 if (!EC_FIXED(t->type->eclass) && t->digits)

Bt:

0 0x00007fffe8b25392 in score_gbe (sql=0x7fffb800ab40, rel=0x7fffb8071a70, e=0x7fffb8072650) at rel_optimizer.c:4841
1 0x00007fffe8b2bee8 in score_se (sql=0x7fffb800ab40, rel=0x7fffb8071a70, e=0x7fffb80726f0) at rel_optimizer.c:6543
2 0x00007fffe8b2c04e in rel_select_order (changes=0x7fffcd3958b4, sql=0x7fffb800ab40, rel=0x7fffb8071a70) at rel_optimizer.c:6559
3 0x00007fffe8b366b5 in rewrite (sql=0x7fffb800ab40, rel=0x7fffb8071a70, rewriter=0x7fffe8b2bf13 <rel_select_order>, has_changes=0x7fffcd395938) at rel_optimizer.c:8821
4 0x00007fffe8b36592 in rewrite (sql=0x7fffb800ab40, rel=0x7fffb80737a0, rewriter=0x7fffe8b2bf13 <rel_select_order>, has_changes=0x7fffcd395938) at rel_optimizer.c:8805
5 0x00007fffe8b370f7 in _rel_optimizer (sql=0x7fffb800ab40, rel=0x7fffb80737a0, g_changes=0x7fffcd3959c0, level=0) at rel_optimizer.c:9017
6 0x00007fffe8b37310 in rel_optimizer (sql=0x7fffb800ab40, rel=0x7fffb80737a0) at rel_optimizer.c:9054
7 0x00007fffe8a17b85 in sql_symbol2relation (c=0x7fffb800ab40, sym=0x7fffb80713e0) at sql.c:121
8 0x00007fffe8a36a35 in SQLparser (c=0x7fffea11d338) at sql_scenario.c:1129
9 0x00007ffff7a14da0 in runPhase (c=0x7fffea11d338, phase=1) at mal_scenario.c:506
10 0x00007ffff7a14ee4 in runScenarioBody (c=0x7fffea11d338) at mal_scenario.c:539
11 0x00007ffff7a15087 in runScenario (c=0x7fffea11d338) at mal_scenario.c:568
12 0x00007ffff7a16c3c in MSserveClient (dummy=0x7fffea11d338) at mal_session.c:473
13 0x00007ffff7a1672c in MSscheduleClient (command=0x7fffb80008d0 "0", challenge=0x7fffcd395deb "B2vJIaPcE", fin=0x7fffb80028f0, fout=0x7fffc4002b70, protocol=PROTOCOL_9, blocksize=8190,
compute_column_widths=0) at mal_session.c:364
14 0x00007ffff7ab9ba6 in doChallenge (data=0x7fffc40008d0) at mal_mapi.c:273
15 0x00007ffff769022a in thread_starter (arg=0x7fffc4004c60) at gdk_system.c:485
16 0x00007ffff4ca336d in start_thread () from /lib64/libpthread.so.0
17 0x00007ffff49dbbbf in clone () from /lib64/libc.so.6

Comment 25760

Date: 2017-10-18 16:59:12 +0200
From: MonetDB Mercurial Repository <>

Changeset e1a77e396b94 made by Pedro Ferreira pedro.ferreira@monetdbsolutions.com in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=e1a77e396b94

Changeset description:

Added test for bug #6435

Comment 25761

Date: 2017-10-19 11:05:17 +0200
From: @njnes

fixed bug in the is_complex_exp macro, solving this problem

Comment 25762

Date: 2017-10-19 11:19:32 +0200
From: MonetDB Mercurial Repository <>

Changeset ee3dd8463f58 made by Niels Nes niels@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=ee3dd8463f58

Changeset description:

fixed bug #6435. cmp_or + anti is properly handled by the is_complex_exp macro
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant