Hello,
since yesterday I have retried to use zendplatform and it's debugger
together with zend studio. (PHP Version is 5.1.6, happened with 5.1.4 too)
We are getting a reproducable segmentation fault as follows:
Program received signal SIGSEGV, Segmentation fault.
0xb79c37db in zend_get_zval_ptr
On Tue, 5 Sep 2006, Mike Bretz wrote:
> since yesterday I have retried to use zendplatform and it's debugger
> together with zend studio. (PHP Version is 5.1.6, happened with 5.1.4 too)
Please report this to the Zend folks as the PHP team has no knowledge
about the platform or their debugger.
r
Please report this to Zend.
Mike Bretz wrote:
Hello,
since yesterday I have retried to use zendplatform and it's debugger
together with zend studio. (PHP Version is 5.1.6, happened with 5.1.4 too)
We are getting a reproducable segmentation fault as follows:
Program received signal SIGSEGV, Se
Hi,
Just over a year ago sniper committed a patch that breaks php.ini search
path for CLI in order to align the behavior with the manual. You can see
his commit message on
http://cvs.php.net/viewvc.cgi/php-src/main/php_ini.c?view=log (revision
1.134).
I regret that this has just come to my attent
Hi all,
I'm afraid that recent changes in filestat.c [1] that were meant to fix
a bug [2] with file_exists() also altered the behaviour of
is_readable(). According to the docs [3] [4], is_readable should *not*
take safe_mode limitations into account, whereas file_exists should do.
[EMAIL PROTE
I think the current behavior solves made old bug reports, where by
people used is_readable() to see if they could read from a file, only
to have the operation file due to safe_mode/open_basedir
restrictions. Taking the check away would also mean it would be
possible to "explore" file file
> I think the current behavior solves made old bug reports,
> where by people used is_readable() to see if they could read
> from a file, only to have the operation file due to
> safe_mode/open_basedir restrictions. Taking the check away
> would also mean it would be possible to "explore" fil
Matthias Pigulla wrote:
Hi all,
I'm afraid that recent changes in filestat.c [1] that were meant to fix
a bug [2] with file_exists() also altered the behaviour of
is_readable(). According to the docs [3] [4], is_readable should *not*
take safe_mode limitations into account, whereas file_exists s
> i dont think this is a recent change. i think its only an
> oversite in the documentation.
[EMAIL PROTECTED]:~$ php ./bug.php
5.1.4
string(0) ""
bool(true)
bool(true)
[EMAIL PROTECTED]:~$ php -d safe_mode=1 ./bug.php
5.1.4
string(1) "1"
bool(true)
bool(true)
With 5.1.4 both file_exists() an
On 5-Sep-06, at 11:45 AM, Matthias Pigulla wrote:
So this is a documentation bug and there is no way to check beforehand
whether an include($filepath) will succeed or not when safe_mode is
on?
Now there is (because of the change), before there was none. Do the
check before, you'd need to
OK well I definitely don't propose to change anything right now.
I was just struck by senility and thought you were discussing making a
chance at this point. I still believe going down the dlls route is better
but it does most probably require some registry changes to make it work well
with IIS. CG
11 matches
Mail list logo
