Just to followup on today's threads on both the strange PHP 4.3.10 apache
coredump/sitting and spinning in malloc() bug #31508 and the losing $this
variable bug 31525.
Both, it turns out, were caused because I was returning references inside
parenthetical expression on return(). i.e.
function &s
> Yermo,
>
> Essentially, what Andi was saying is that we need your help in order for
> us to help you. To put it more clearly - even if there is a bug in the
> language engine or some other component of PHP - it's impossible for us to
> figure out what it is, unless we're provided with a reprodu
Yermo,
Essentially, what Andi was saying is that we need your help in order for us
to help you. To put it more clearly - even if there is a bug in the
language engine or some other component of PHP - it's impossible for us to
figure out what it is, unless we're provided with a reproducible test
> I'll go through your email later but note that E_STRICT is not part of
E_ALL. Please run E_ALL|E_STRICT
Interestingly enough, although E_ALL|E_STRICT generates the correct
return() error message in the test case, it does /NOT/ generate any such
error messages when running the full body of my p
> I'll go through your email later but note that E_STRICT is not part of
> E_ALL. Please run E_ALL|E_STRICT
Learn something new every day. Disregard. I had always thought E_STRICT
was part of E_ALL. (And if I could read I would see it clearly states that
in php.ini )
With E_STRICT turned on
Andi,
Thanks for the return() pointer .. I figure that's probably what's causing
alot of my trouble.
> You have to understand that with the amount of work we're doing on PHP,
> it's very hard to start logging into someone's server (many offer) and
> debug 61K of code we don't know.
That's not wh
I'll go through your email later but note that E_STRICT is not part of
E_ALL. Please run E_ALL|E_STRICT
Thanks.
At 09:35 PM 3/5/2005 -0500, Yermo Lamers wrote:
Andi,
> Are you getting an error message if you set E_STRICT?
I always run E_ALL. I've noticed that warnings and error messages are
quite
Andi,
> Are you getting an error message if you set E_STRICT?
I always run E_ALL. I've noticed that warnings and error messages are
quite sporadic. Upgrade a minor revision and code that worked before
suddenly fails with errors.
> Actually this code is not supposed to work in the first place. Th
Hi Jermo,
Are you getting an error message if you set E_STRICT?
Actually this code is not supposed to work in the first place. The reason
is that you are only allowed to return variables by reference (like in many
other languages). There was a bug in PHP 4 and early versions of PHP 5
which allow
Yermo,
You have to understand that with the amount of work we're doing on PHP,
it's very hard to start logging into someone's server (many offer) and
debug 61K of code we don't know. It also means that instead of you spending
the time to try and reproduce it, one of the PHP Development team woul
Thanks to michaels (at) crye-leike.com for the followup. He produced a
much shorter version of the code that produces the same result:
getThis();
}
}
$bar = new Foo();
$bar->destroyThis();
var_dump($bar);
?>
Interestingly if you change the return( $this ) in &getThis() to return
$this; the bug
> The problem you're having is not giving the right information. For
> instance, the buffer overrun errors would be an ideal thing to attach
> to your bug report.
The buffer overruns are the separate bug in PHP 4 as in
http://bugs.php.net/31508.
The PHP 5 is not encountering a buffer overrun; i
On Sat, 5 Mar 2005 16:05:45 -0500 (EST), Yermo Lamers <[EMAIL PROTECTED]> wrote:
> At least with --enable-debug turned on the coredump problems goes away and
> it generates very nice buffer overrun errors.
> Like I said, I haven't had much luck reporting bugs. No problem. I
> understand they are
> Yermo Lamers wrote:
>> I've not had alot of luck with reporting bugs through the bug tracker;
>> For instance see
>>
>> http://bugs.php.net/31508
>>
>> where the guy claims PHP can't do recursion without crashing ... Ummm?
>
> To be fair, he is correct in what he says; PHP cannot do recursion
Yermo Lamers wrote:
I've not had alot of luck with reporting bugs through the bug tracker;
For instance see
http://bugs.php.net/31508
where the guy claims PHP can't do recursion without crashing ... Ummm?
To be fair, he is correct in what he says; PHP cannot do recursion
beyond a certain level,
PHP 5.0.3 is losing $this. PHP 4.3.10 and 5.0.0 seem to work fine.
The bug originally appeared in 5.0.2.
I have submitted a bug report at:
http://bugs.php.net/31525
I've not had alot of luck with reporting bugs through the bug tracker;
For instance see
http://bugs.php.net/31508
where the guy cl
16 matches
Mail list logo
