[PHP-DEV] PHP 4.0 Bug #9463: cmd line PHP crash with oracle+oci loaded

[g . giunta]

From: [EMAIL PROTECTED]
Operating system: Windows 95
PHP version:  4.0.4pl1
PHP Bug Type: Oracle related
Bug description:  cmd line PHP crash with oracle+oci loaded

When run from the command line, php 4.04pl1 (or 4.03pl1) will crash if both oracle and 
oci extensions are loaded.
Funny enough this happens when invoking 'php -h' and not with 'php -i'...

OS: win95 osr2 ita
ORACLE: client 8.05+7.3.4
PHP: 4.03pl1 / 4.04pl1 (version from php.net)

Error reported by windows:

PHP ha provocato un errore di pagina non valida nel
modulo PHP4TS.DLL in 013f:1005603f.
Registri:
EAX= CS=013f EIP=1005603f EFLGS=00010286
EBX= SS=0147 ESP=0063ec8c EBP=006a798c
ECX= DS=0147 ESI= FS=a1e7
EDX=002c ES=0147 EDI=002c GS=
Byte all'indirizzo CS:EIP:
f2 ae f7 d1 49 89 55 48 89 4d 4c 41 89 4d 50 8b 
Immagine dello stack:
000a  027a 0063ed2c 007b0370 bff798cf 817a3660 007deaf0 10089be0 
007b0600 100482aa 0063ed2c 027a 007c20b0 002c 0063ecf0 

Ini file:

[PHP]

;;;
; About this file ;
;;;
; This file controls many aspects of PHP's behavior.  In order for PHP to
; read it, it must be named 'php.ini'.  PHP looks for it in the current
; working directory, in the path designated by the environment variable
; PHPRC, and in the path that was defined in compile time (in that order).
; Under Windows, the compile-time path is the Windows directory.  The
; path in which the php.ini file is looked for can be overriden using
; the -c argument in command line mode.
;
; The syntax of the file is extremely simple.  Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
;
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from FOO=bar.
;
; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
;
; Expressions in the INI file are limited to bitwise operators and parentheses:
; | bitwise OR
; & bitwise AND
; ~ bitwise NOT
; ! boolean NOT
;
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
;
; An empty string can be denoted by simply not writing anything after the equal
; sign, or by using the None keyword:
;
;   foo =   ; sets foo to an empty string
;   foo = none  ; sets foo to an empty string
;   foo = "none"; sets foo to the string 'none'
;
; If you use constants in your value, and these constants belong to a dynamically
; loaded extension (either a PHP extension or a Zend extension), you may only
; use these constants *after* the line that loads the extension.
;
; All the values in the php.ini-dist file correspond to the builtin
; defaults (that is, if no php.ini is used, or if you delete these lines,
; the builtin defaults will be identical).



; Language Options ;


engine  =   On  ; Enable the PHP scripting language engine 
under Apache
short_open_tag  =   On  ; allow the  tags are recognized.
asp_tags=   Off ; allow ASP-style <% %> tags
precision   =   14  ; number of significant digits displayed in 
floating point numbers
y2k_compliance  =   Off ; whether to be year 2000 compliant (will cause 
problems with non y2k compliant browsers)
output_buffering= Off   ; Output buffering allows you to send header lines 
(including cookies)
; even after you send body 
content, in the price of slowing PHP's
; output layer a bit.
; You can enable output 
buffering by in runtime by calling the output
; buffering functions, or 
enable output buffering for all files
; by setting this directive to 
On.
output_handler  =   ; You can redirect all of the output of your 
scripts to a function,
; that can be responsible to 
process or log it.  For example,
; if you set the 
output_handler to "ob_gzhandler", than output
; will be transparently 
compresse

[PHP-DEV] PHP 4.0 Bug #9520: After a call to OCIFetchStatement functions on stament do not work anymore

[g . giunta]

From: [EMAIL PROTECTED]
Operating system: Windows
PHP version:  4.0.4pl1
PHP Bug Type: OCI8 related
Bug description:  After a call to OCIFetchStatement functions on stament do not work 
anymore

After a call to OCIFetchInto, functions ocirowcount, ocicolumnname, ocicolumnsize, 
ocicolumnisnull will NOT work anymore on the fetched statement.

Oci client: 8.0.5 on windows 95

PHP version: 4.0.4pl1 (got from php.net)

copy of php.ini:

[PHP]

;;;
; About this file ;
;;;
; This file controls many aspects of PHP's behavior.  In order for PHP to
; read it, it must be named 'php.ini'.  PHP looks for it in the current
; working directory, in the path designated by the environment variable
; PHPRC, and in the path that was defined in compile time (in that order).
; Under Windows, the compile-time path is the Windows directory.  The
; path in which the php.ini file is looked for can be overriden using
; the -c argument in command line mode.
;
; The syntax of the file is extremely simple.  Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
;
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from FOO=bar.
;
; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
;
; Expressions in the INI file are limited to bitwise operators and parentheses:
; | bitwise OR
; & bitwise AND
; ~ bitwise NOT
; ! boolean NOT
;
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
;
; An empty string can be denoted by simply not writing anything after the equal
; sign, or by using the None keyword:
;
;   foo =   ; sets foo to an empty string
;   foo = none  ; sets foo to an empty string
;   foo = "none"; sets foo to the string 'none'
;
; If you use constants in your value, and these constants belong to a dynamically
; loaded extension (either a PHP extension or a Zend extension), you may only
; use these constants *after* the line that loads the extension.
;
; All the values in the php.ini-dist file correspond to the builtin
; defaults (that is, if no php.ini is used, or if you delete these lines,
; the builtin defaults will be identical).



; Language Options ;


engine  =   On  ; Enable the PHP scripting language engine 
under Apache
short_open_tag  =   On  ; allow the  tags are recognized.
asp_tags=   Off ; allow ASP-style <% %> tags
precision   =   14  ; number of significant digits displayed in 
floating point numbers
y2k_compliance  =   Off ; whether to be year 2000 compliant (will cause 
problems with non y2k compliant browsers)
output_buffering= Off   ; Output buffering allows you to send header lines 
(including cookies)
; even after you send body 
content, in the price of slowing PHP's
; output layer a bit.
; You can enable output 
buffering by in runtime by calling the output
; buffering functions, or 
enable output buffering for all files
; by setting this directive to 
On.
output_handler  =   ; You can redirect all of the output of your 
scripts to a function,
; that can be responsible to 
process or log it.  For example,
; if you set the 
output_handler to "ob_gzhandler", than output
; will be transparently 
compressed for browsers that support gzip or
; deflate encoding.  Setting 
an output handler automatically turns on
; output buffering.
implicit_flush  = Off   ; Implicit flush tells PHP to tell the output layer to 
flush itself
; automatically after every 
output block.  This is equivalent to
; calling the PHP function 
flush() after each and every call to print()
  

[PHP-DEV] PHP 4.0 Bug #9787: redirecting php-cgi stderr does not affect php://stderr

[g . giunta]

From: [EMAIL PROTECTED]
Operating system: SCO Openserver5 (Any UNIX?)
PHP version:  4.0.4pl1
PHP Bug Type: Filesystem function related
Bug description:  redirecting php-cgi stderr does not affect php://stderr

Redirecting php-cgi stderr when invoking a php script from the command line (as in 
'myscript.php 2>error.log') does not affect writing data to php://stderr, but it does 
affect writing to /dev/stderr.



-- 
Edit Bug report at: http://bugs.php.net/?id=9787&edit=1



-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

[PHP-DEV] Bug #11550: Cannot return a NULL as out parameter of a stored procedure

[g . giunta]

From: [EMAIL PROTECTED]
Operating system: Windows 95; SCO Openserver 5.0.5
PHP version:  4.0.4pl1
PHP Bug Type: Oracle related
Bug description:  Cannot return a NULL as out parameter of a stored procedure

Returning a NULL value as an OUT parameter of a stored procedure (oracle 7.3.4 both 
client & server) I get the following error from a call to ora_exec: 

ORA-01405: fetched column value is NULL -- 
while processing OCI function OEXEC/OEXN 

I've checked the parameter is correctly bound to a php global variable. 

I tried defining the same parameter both as OUT and IN_OUT, to no avail. 

I also tried calling the same exact procedure using oci_ functions instead of ora_, 
and everything works! (Unfortunately my web server is sitting on a sco box, so I'm 
doomed to use oracle 7.3.4 in production...) 

Looking at the description of the error in oracle manuals, I think this could be a pbl 
in the use of pro*C (well, whatever the php oracle extension is written with), but I 
might be wrong


-- 
Edit Bug report at: http://bugs.php.net/?id=11550&edit=1



-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]