ID: 38161
Updated by: [EMAIL PROTECTED]
Reported By: a dot bodemer at brillux dot de
Status: Open
Bug Type: OCI8 related
Operating System: Linux x86
PHP Version: 5.1.4
New Comment:
Actually I have a workaround, but I'm still waiting for feedback from
Oracle people - it looks like the problem is in Oracle itself, since
Oracle should not call the callback if it's not going to set variable's
value and if it finally called it - it should at least say there was no
value.
Since there is no way to detect "called, but no value set" situation,
the workaround is apparently pretty ugly.
Previous Comments:
------------------------------------------------------------------------
[2006-07-28 11:55:18] a dot bodemer at brillux dot de
Hello toni,
it is not the problem to implement a workaround. I meen it
is important find the bug. May be there is more than this?
I doen't hope it.
------------------------------------------------------------------------
[2006-07-28 01:00:01] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2006-07-21 03:36:55] cjbj at hotmail dot com
Tony you shouldn't need a stack dump for this. Just try a
var_dump($returnValue) at the end of the script. Because no value has
been returned in the variable it is being treated as a 64K string and
printing garbage.
The workaround for users is to make sure that the PL/SQL block always
sets variable values in all possible code paths. Something like:
$query= "declare
n_status NUMBER(2);
begin
:retValue := 0; -- set default value
n_status := 1 ;
IF :n_status = 0 THEN
:retValue := :n_status;
END IF;
end;";
------------------------------------------------------------------------
[2006-07-20 15:48:02] [EMAIL PROTECTED]
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32
Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.
------------------------------------------------------------------------
[2006-07-20 15:05:00] a dot bodemer at brillux dot de
The SampleCode produce in php5.2-200607190630 the same result, a memory
dump.
In all Testcases the script run without a PHP Error message or a
'Segmentation Failure'.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/38161
--
Edit this bug report at http://bugs.php.net/?id=38161&edit=1
