<< PSQL bugs | Firebird 2.0.7 Release Notes | Remote interface bugs >>

Bugs fixed


Firebird 2.0: Crash conditions


Not registered A crash could occur if some bad client passed more than the supported number of remote protocol versions.

fixed by A. Karyakin, A. Peshkov

~ ~ ~

Not registered An AV could occur when the server was configured to use TCP packets as large as 32 Kb.

fixed by C. Valderrama, A. Peshkov

~ ~ ~

Not registered Server would crash if a positioned UPDATE/DELETE executed via DSQL was referencing a cursor that had already been released.

fixed by V. Horsun

~ ~ ~

Not registered Certain DDL actions could crash the server.

Example of a problem action

 alter table rdb$relations
 add rdb$garbage varchar(30);

fixed by J. Starkey

~ ~ ~

Not registered An overflow in the plan buffer would cause the server to crash.

fixed by D. Yemanov

~ ~ ~

Not registered Possible server lockup/crash when RELEASE SAVEPOINT xxx ONLY syntax is used or when existing savepoint name is reused in transaction context.

fixed by N. Samofatov

~ ~ ~

Not registered Rare client crashes caused by improperly cleaned XDR packets.

fixed by D. Yemanov

~ ~ ~

Not registered Server crash during SuperServer shutdown

fixed by A. Peshkov

~ ~ ~

SF #1057538 The server would crash if the output parameter of a UDF was not the last parameter.

fixed by C. Valderrama

~ ~ ~

Not registered A number of possible server crash conditions had been reported by Valgrind.

fixed by N. Samofatov

~ ~ ~

Not registered Server would crash when a wrong type or domain name was specified when changing the data type for a column.

fixed by N. Samofatov

~ ~ ~

Not registered Incorrect accounting of attachment pointers used inside the lock structure was causing the server to crash.

fixed by N. Samofatov

~ ~ ~

Not registered In v.1.5, random crashes would occur during a restore.

fixed by J. Starkey

~ ~ ~

Not registered Crash/lock-up with multiple calls of isc_dsql_prepare for a single statement.

fixed by N. Samofatov

~ ~ ~

Not registered Server would crash when the system year was set too high or too low.

fixed by D. Yemanov

~ ~ ~

Not registered Server would crash when the stream number exceeded the limit.

fixed by D. Yemanov

~ ~ ~

Not registered Server would crash when outer aggregation was performed and explicit plans were used in subqueries.

fixed by D. Yemanov

~ ~ ~

Not registered DECLARE FILTER would cause the server to crash.

fixed by A. Peshkov

~ ~ ~

Not registered The server would crash when a PLAN for a VIEW was specified but no table alias was given.

fixed by V. Horsun

~ ~ ~

Not registered Server would crash during the table metadata scan in some cases.

fixed by D. Yemanov

~ ~ ~

Not registered Server would crash when too big a key was specified for an index retrieval.

fixed by D. Yemanov

~ ~ ~

Not registered Server would crash when manipulating input DPB due to memory corruption in Parameter Blocks management.

fixed by C. Valderrama

~ ~ ~

Not registered Server would crash when attempting to restore a database backup with corrupted VARCHAR data.

fixed by D. Yemanov

~ ~ ~

back to top of page
<< PSQL bugs | Firebird 2.0.7 Release Notes | Remote interface bugs >>