You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems IBO copies handle value into new variable after isc_dsql_alloc_statement2() and later deleted original variable which was used to initially obtain handle value.
Taking into an account, that "isc_dsql_allocate_statement2()
function is similar to the isc_dsql_alloc_statement() function except that
statement handles allocated using isc_dsql_allocate_statement2() are
automatically reset to NULL when the database under which they are allocated
is detached" (taken from ib6.0 beta docs), this is close to violation of API rules. On the other hand, nothing is said about isc_dsql_free_statement(), and if IBO itself releases all statements before detach, it works correctly. (Though there is no use in isc_dsql_allocate_statement2() instead of isc_dsql_allocate_statement() in that case.)
Legacy behavior of isc_dsql_free_statement() is restored.
Submitted by: @AlexPeshkoff
When releasing statement with isc_dsql_free_statement(), AV happens in client library
Commits: b474ff2 dceac94
The text was updated successfully, but these errors were encountered: