Interbase bug #15419 - #15992 (proposal)

EXTENSION: interbase PRIMARY MAINTAINER: Jouni Ahto MAINTENANCE: Odd Fixes STATUS: Working Hello Jouni , Following up from bug #15419 and #15992 I finally :) found a (good ?) solution to avoid segmentation fault .... so, I would like to let you know about the way I thought to fix it. Actually, the problem lies in resources release during shutdown process if a user close a connection without explicitly specify to release its query or resultset .... Sigfault is due to the calling to an IB Api when DB is already closed. This calling raise an error ..... but the buffer (global) to handle the error message is already released too ....... crash!!!!!!!! I think we can solve this, in two different ways: 1) it would be possible to skip the raise error step... but it doesn't seem to me the correct way to solve the problem ......... or 2) it would be possible to test if we have the relative transaction open. ... if so ... then we can proceed to release the statement .... otherwise .... we have nothing to do ......... I 've choosen this second way in the patch (see attach) If you have no objections ... I 'm going to commit this patch in CVS, or let me know your opinion , any suggestion is really appreciated .............. Daniela

Attachment: [application/octet-stream] Bug15419.diff