If we create the following function:
CREATE FUNCTION f1(specObjIdd bigint)
RETURNS varchar(128)
BEGIN
DECLARE link varchar(128);
RETURN link;
END;
And then we re-start the mserver, but this time in readonly mode, the call of the function:
select f1(3) as url;
gives the following message at the mserver:
schema statements cannot be executed on a readonly database.
at the mclient it reports:
ERROR = !schema statements cannot be executed on a readonly database.
!TypeException:user.s0_1[4]:'user.f1' undefined in: _6:any := user.f1(_5:lng)
and when the mclient is closed the mserver crashes:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe862f710 (LWP 20719)]
0x000000383ae7fcb2 in __strlen_sse2 () from /lib64/libc.so.6
(gdb) up
1 0x00007fffe8aa47b6 in SQLparser (c=0x605238)
at /ufs/goncalve/MonetDB/current/sql/src/backends/monet5/sql_scenario.mx:1327
1327 be->q->name = putName(be->q->name, strlen(be->q->name));
(gdb) p be->q->name
$1 = 0xdbdbdbdbdbdbdbdb <Address 0xdbdbdbdbdbdbdbdb out of bounds>
(gdb) bt
0 0x000000383ae7fcb2 in __strlen_sse2 () from /lib64/libc.so.6
1 0x00007fffe8aa47b6 in SQLparser (c=0x605238)
at /ufs/goncalve/MonetDB/current/sql/src/backends/monet5/sql_scenario.mx:1327
2 0x00007ffff708317e in runPhase (c=0x605238, phase=1)
at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_scenario.mx:604
3 0x00007ffff70832ad in runScenarioBody (c=0x605238)
at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_scenario.mx:646
4 0x00007ffff7083452 in runScenario (c=0x605238)
at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_scenario.mx:682
5 0x00007ffff708442f in MSserveClient (dummy=0x605238)
at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_session.mx:484
6 0x000000383ba068e0 in start_thread () from /lib64/libpthread.so.0
7 0x000000383aee0c9d in clone () from /lib64/libc.so.6
8 0x0000000000000000 in ?? ()
(gdb)
Date: 2010-11-09 14:08:17 +0100
From: @romulogoncalves
To: SQL devs <>
Version: 2.40.1 (Oct2010) [obsolete]
CC: @njnes
Last updated: 2011-03-28 17:31:33 +0200
Comment 15184
Date: 2010-11-09 14:08:17 +0100
From: @romulogoncalves
If we create the following function:
CREATE FUNCTION f1(specObjIdd bigint)
RETURNS varchar(128)
BEGIN
DECLARE link varchar(128);
RETURN link;
END;
And then we re-start the mserver, but this time in readonly mode, the call of the function:
select f1(3) as url;
gives the following message at the mserver:
schema statements cannot be executed on a readonly database.
at the mclient it reports:
ERROR = !schema statements cannot be executed on a readonly database.
!TypeException:user.s0_1[4]:'user.f1' undefined in: _6:any := user.f1(_5:lng)
and when the mclient is closed the mserver crashes:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe862f710 (LWP 20719)]
0x000000383ae7fcb2 in __strlen_sse2 () from /lib64/libc.so.6
(gdb) up
1 0x00007fffe8aa47b6 in SQLparser (c=0x605238)
at /ufs/goncalve/MonetDB/current/sql/src/backends/monet5/sql_scenario.mx:1327
1327 be->q->name = putName(be->q->name, strlen(be->q->name));
(gdb) p be->q->name
$1 = 0xdbdbdbdbdbdbdbdb <Address 0xdbdbdbdbdbdbdbdb out of bounds>
(gdb) bt
0 0x000000383ae7fcb2 in __strlen_sse2 () from /lib64/libc.so.6
1 0x00007fffe8aa47b6 in SQLparser (c=0x605238)
at /ufs/goncalve/MonetDB/current/sql/src/backends/monet5/sql_scenario.mx:1327
2 0x00007ffff708317e in runPhase (c=0x605238, phase=1)
at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_scenario.mx:604
3 0x00007ffff70832ad in runScenarioBody (c=0x605238)
at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_scenario.mx:646
4 0x00007ffff7083452 in runScenario (c=0x605238)
at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_scenario.mx:682
5 0x00007ffff708442f in MSserveClient (dummy=0x605238)
at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_session.mx:484
6 0x000000383ba068e0 in start_thread () from /lib64/libpthread.so.0
7 0x000000383aee0c9d in clone () from /lib64/libc.so.6
8 0x0000000000000000 in ?? ()
(gdb)
Comment 15239
Date: 2010-12-01 23:06:28 +0100
From: @njnes
this bug is fixed.
Comment 15633
Date: 2011-03-28 17:31:33 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
The text was updated successfully, but these errors were encountered: