Description:
------------
Binding a cursor to a PL/SQL function that returns a cursor causes a segmentation fault in the PHP-OCI code when the PL/SQL function is called more than once.

While this isn't a strictly correct, as it leaves a dangling cursor, it doesn't crash PHP4 (which I am migrating from).

I've collected more information which is available at:
http://goanna.cs.rmit.edu.au/~geoffwa/oci8_php_crash/index.html


Reproduce code:
---------------
// Abbreivated example - assume connected $dbh and
// function that returns cursor
$query = "BEGIN :v_cursor := some_function(); END;";
$cursor = oci_new_cursor($dbh);
$sth = oci_parse($dbh, $query);
oci_bind_by_name($sth, ':v_cursor', $cursor,
   -1, OCI_B_CURSOR);
oci_execute($sth);
oci_execute($cursor);
oci_fetch_array($cursor);
oci_free_statment($sth);
oci_free_statment($cursor);
$sth = oci_parse($dbh, $query);
$cursor = oci_new_cursor($dbh);
oci_bind_by_name($sth, ':v_cursor', $cursor,
   -1, OCI_B_CURSOR);
oci_execute($sth); // <-- crash here
oci_execute($cursor);
oci_fetch_array($cursor);
oci_free_statment($sth);
oci_free_statment($cursor);

Expected result:
----------------
I expect the code to execute successfully, to not crash PHP, and to cleanup the cursors when the database handle is closed.