Executing RDB$RESET_CONTEXT() without parameters kills the connection

[mrotteveel]

On Firebird 5.0.4 (and snapshot LI-V5.0.5.1832 Firebird 5.0 0fe01b3), executing RDB$RESET_CONTEXT() without parameters kills the connection:

root@8ad5b53a02e1:/# isql -user sysdba -password masterkey localhost:testdb.fdb
Database: localhost:testdb.fdb, User: SYSDBA
SQL> select rdb$reset_context() from rdb$database;
Statement failed, SQLSTATE = 08006
Error reading data from the connection.
SQL> exit;
Statement failed, SQLSTATE = 08006
Error writing data to the connection.
Statement failed, SQLSTATE = 08006
Error writing data to the connection.
root@8ad5b53a02e1:/# 

On Firebird 6.0 snapshot, this correctly reports

SQL> select rdb$reset_context() from rdb$database;
Statement failed, SQLSTATE = 39000
function RDB$RESET_CONTEXT could not be matched

Trying to call the function on 5.0.4/5.0.5 snapshot with too many parameters correctly reports "function RDB$RESET_CONTEXT could not be matched".

[mrotteveel]

When using an embedded connection, it results in:

root@20ac21f234ec:/# isql -user sysdba testdb.fdb
Database: testdb.fdb, User: SYSDBA
SQL> select rdb$reset_context() from rdb$database;
Segmentation fault (core dumped)
root@20ac21f234ec:/# 

(I haven't been able to locate the core dump)

[hvlad]

The problem is not with RDB$RESET_CONTEXT(), is it more generic and affects more built-in functions.
It were fixed in #8242, but not backported

[hvlad]

@dyemanov: is there a reason to not backport #8242 ?
If not, do you want me to do it ?

[dyemanov]

Surely worth backporting, I believe.

[hvlad]

Fixed in #8242, backported into v5 and v4