Bugs Fixed

(CORE-6043)     Space used by global temporary tables (GTTs) was not being released.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6015)     Use of an expression index with a complex expression could cause a segfault.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5935)     Bugcheck 165 (cannot find tip page) could occur under some conditions.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5847)     When a client connected using the UTF8 character set and a PK violation occurred on a character key, the second-level error returned was “Malformed string” instead of the offending key value.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5800)     Expression indexes on computed fields were not working properly following a backup-and-restore.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5762)     A wrong transaction number in the system table RDB$PAGES could give rise to infinite recursion and eventually a segfault.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5757)     Deadlock with events in multiple threads.

fixed by A. Peshkoff

    ~ ~ ~     

(CORE-5685)     Sometimes it was not possible to cancel\kill a connection that was executing an external query.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5074)     The character set ID was lost when selecting an array element.

fixed by D. Kovalenko

    ~ ~ ~     

(CORE-5017)     Interruption of the auxiliary (events) connection during the TCP setup phase could cause the server to exit due to an unhandled exception.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5014)     Interrruption of the disconnect during queEvents() would return obscure network error messages to the firebird.log.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4565)     On Classic and Superclassic, a GDSCODE could have value of zero in the WHEN section of a PSQL block in some conditions where multiple connections were working on the same data.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6064)     Segfaults could occur when DDL operations were performed against Stored Procedures under multi-user load.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6054)     A possible collation issue could cause the 64-bit fb_inet_server to crash randomly.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5980)     Firebird could crash during concurrent operations with expression indices.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5943)     The server could crash preparing a query having DISTINCT or ORDER BY together with a non-field expression in the select list.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5939)     The nul device can be used as the target for a backup, e.g., gbak -b host/port:alias nul. However, when used with the -se[rvice_mgr] switch, this form would cause a crash.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5936)     The Firebird server could crash at the end of a gbak backup.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5910)     A destructor fault in the EDS manager could crash the server after a kill operation.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6007)     Firebird would not build on a Mac with a fresh toolchain.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5868)     The Darwin build of fbintl (libfbintl.dylib) was exporting all functions, including new and delete, because the makefile darwin.defaults was not passing the symbols list to the linker.

fixed by P. Beach

    ~ ~ ~