On Fri, 19 Dec 2003 02:22:06 +0200
Andi Gutmans <[EMAIL PROTECTED]> wrote:
> So the revert I did 20 minutes ago didn't help?
It was with the last snapshot, I´m going to checkout
it now and test again...
Anything else can I send that could help?
Eduardo R. Maciel
___
On Fri, 19 Dec 2003 01:42:04 +0100
Pierre-Alain Joye <[EMAIL PROTECTED]> wrote:
> On Fri, 19 Dec 2003 02:22:06 +0200
> Andi Gutmans <[EMAIL PROTECTED]> wrote:
>
> > So the revert I did 20 minutes ago didn't help?
>
> Fresh check out. Same problem. It crashes in normal mode. No crash
> (but the "
On Fri, 19 Dec 2003 02:22:06 +0200
Andi Gutmans <[EMAIL PROTECTED]> wrote:
> So the revert I did 20 minutes ago didn't help?
Fresh check out. Same problem. It crashes in normal mode. No crash (but
the "... being destroyed") message.
Anything I can do to help more? As said in my previous post the
Andi Gutmans wrote:
Did this specific test work before I reverted Dmitry's patch?
There were three changes in his patch, maybe one of them caused the
crash and one of them fixed the problem you are mentioning.
Andi
with yesterdays Beta3RC1 this test worked.
johannes
--
PHP Internals - PHP Runt
Did this specific test work before I reverted Dmitry's patch?
There were three changes in his patch, maybe one of them caused the crash
and one of them fixed the problem you are mentioning.
Andi
At 01:24 AM 12/19/2003 +0100, Johannes Schlueter wrote:
Pierre-Alain Joye wrote:
With --enabled-deb
Pierre-Alain Joye wrote:
With --enabled-debug it reports a memory leak but it works again.
/home/johannes/src/php-cvs/php-src/Zend/zend_execute.c(405) : Freeing
Does it crash again without --enabled-debug? That's what I got before.
Crash without, works with.
Ah, I didn't run make test -
So the revert I did 20 minutes ago didn't help?
Andi
At 04:06 PM 12/18/2003 -0800, Eduardo R. Maciel wrote:
For me it has been crashing for about 10 days ago to
now:
[EMAIL PROTECTED]:/usr/src/php5-200312182030# make
install-pear-packages
[PEAR] DB - already installed: 1.5.0RC1
[PEAR
For me it has been crashing for about 10 days ago to
now:
[EMAIL PROTECTED]:/usr/src/php5-200312182030# make
install-pear-packages
[PEAR] DB - already installed: 1.5.0RC1
[PEAR] HTTP - already installed: 1.2.1
make: *** [install-pear-packages] Falha de segmentação
config.ni
On Fri, 19 Dec 2003 00:47:06 +0100
Johannes Schlueter <[EMAIL PROTECTED]> wrote:
> With --enabled-debug it reports a memory leak but it works again.
>
> /home/johannes/src/php-cvs/php-src/Zend/zend_execute.c(405) : Freeing
Does it crash again without --enabled-debug? That's what I got before.
C
Okay great. So I'll re-roll B3.
We will have to look into the bugs these patches were supposed to fix after
B3. They aren't very critical.
Andi
At 12:47 AM 12/19/2003 +0100, Johannes Schlueter wrote:
With --enabled-debug it reports a memory leak but it works again.
/home/johannes/src/php-cvs/ph
With --enabled-debug it reports a memory leak but it works again.
/home/johannes/src/php-cvs/php-src/Zend/zend_execute.c(405) : Freeing
0x406B0508 (16 bytes),
script=/home/johannes/src/php-cvs/php-src/pear/install-pear.php
=== Total 1 memory leaks detected ===
johannes
Andi Gutmans wrote:
Ca
Can you please update the Zend CVS and see if it still crashes? I reverted
some recent engine patches.
Thanks,
Andi
At 12:30 AM 12/19/2003 +0100, Johannes Schlueter wrote:
Stig S. Bakken wrote:
Could someone with a crashing "make install-pear-packages" post the
contents of their config.nice fil
Stig S. Bakken wrote:
Could someone with a crashing "make install-pear-packages" post the
contents of their config.nice file
this gives a segfault:
CC='gcc' \
CXX='g++' \
'./configure' \
'--prefix=/opt/php5' \
"$@"
this tells "/home/johannes/src/php-5.0.0b3RC1/Zend/zend_hash.c(504) :
ht=0x40672f
Andrey Hristov wrote:
That's your view :)
Exactly.
E_NOTICEs exists for good not for bad. If one codes a simple web
interface it's ok for him to use
the autoinitialization but in 99.999% of the cases the user won't use
And that's _your_ view ;-)
[EMAIL PROTECTED]:/sample_project $ find -type f
Christian Schneider wrote:
Andrey Hristov wrote:
Good question. Having an error handling function becomes really
expensive if your code is not E_ALL-clean in a loop or something.
if you set a custom error handler you know what you are doing
and probably don't have such places in the code :)
Andrey Hristov wrote:
Good question. Having an error handling function becomes really
expensive if your code is not E_ALL-clean in a loop or something.
if you set a custom error handler you know what you are doing
and probably don't have such places in the code :)
No, that's where you are wrong:
On Thu, 18 Dec 2003, Stig S. Bakken wrote:
> > Anyway, I'm holding off with Beta 3 until we fix the
> > --install-pear-packages problem. I'd call that a showstopper because it's
> > something pretty basic.
> > Has anyone managed to create a reproducing script or backtrace?
>
> It doesn't crash on
Stig S. Bakken wrote:
Good question. Having an error handling function becomes really
expensive if your code is not E_ALL-clean in a loop or something.
if you set a custom error handler you know what you are doing
and probably don't have such places in the code :)
IMHO the error_reporting ma
On Thu, 2003-12-18 at 23:24, Derick Rethans wrote:
> On Thu, 18 Dec 2003, Christian Schneider wrote:
>
> > In case someone now cries "but then I need to change php.ini" I'd say
> > you have to change php.ini for PHP5 anyway.
>
> That is FUD.
>
> > Come on guys, there's no better time to fix the
On Thu, 18 Dec 2003, Christian Schneider wrote:
> In case someone now cries "but then I need to change php.ini" I'd say
> you have to change php.ini for PHP5 anyway.
That is FUD.
> Come on guys, there's no better time to fix the behaviour than now.
yeah, and you should be the one to decide that
Christian Schneider wrote:
Andrey Hristov wrote:
Look like I am an weirdo :) with an web farm of servers which log
every NOTICE that appear. And even I think it was possible to catch
a fatal error that happens in a required file with the way the
error handler works now.
And what exactly keeps y
On Thu, 2003-12-18 at 22:56, Andi Gutmans wrote:
> At 10:24 PM 12/18/2003 +0100, Derick Rethans wrote:
> >On Thu, 18 Dec 2003, Andi Gutmans wrote:
> >
> > > In any case, I do think that the custom error handler being called for any
> > > error is bogus. Why should E_STRICT or E_NOTICES be sent to t
On Thu, 2003-12-18 at 20:35, Andi Gutmans wrote:
> At 07:20 PM 12/18/2003 +0100, Christian Schneider wrote:
> >Derick Rethans wrote:
> >>It won't bork all scripts with a custom errorhandler if their default
> >>action is to ignore core and other errors but only handle the ones they
> >>should handl
Andrey Hristov wrote:
Look like I am an weirdo :) with an web farm of servers which log
every NOTICE that appear. And even I think it was possible to catch
a fatal error that happens in a required file with the way the
error handler works now.
And what exactly keeps you from setting error_reporting
Andi Gutmans wrote:
At 10:24 PM 12/18/2003 +0100, Derick Rethans wrote:
On Thu, 18 Dec 2003, Andi Gutmans wrote:
> In any case, I do think that the custom error handler being called
for any
> error is bogus. Why should E_STRICT or E_NOTICES be sent to the
handler if
> they are off?
So you're
On Thu, 18 Dec 2003, Andi Gutmans wrote:
> At 10:24 PM 12/18/2003 +0100, Derick Rethans wrote:
> >On Thu, 18 Dec 2003, Andi Gutmans wrote:
> >
> > > In any case, I do think that the custom error handler being called for any
> > > error is bogus. Why should E_STRICT or E_NOTICES be sent to the hand
At 10:24 PM 12/18/2003 +0100, Derick Rethans wrote:
On Thu, 18 Dec 2003, Andi Gutmans wrote:
> In any case, I do think that the custom error handler being called for any
> error is bogus. Why should E_STRICT or E_NOTICES be sent to the handler if
> they are off?
So you're suggesting to add another
Derick Rethans wrote:
So you're suggesting to add another BC break here, without a really
good reason? :)
No, I'm suggesting a very minor BC break for a very good reason: To
render it useful, after all (-:C
- Chris
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: ht
On Thu, 18 Dec 2003, Andi Gutmans wrote:
> In any case, I do think that the custom error handler being called for any
> error is bogus. Why should E_STRICT or E_NOTICES be sent to the handler if
> they are off?
So you're suggesting to add another BC break here, without a really
good reason? :)
D
In a test I´ve done, doing:
php5 -dshort_open_tag=0 -dsafe_mode=0
/usr/src/php5-200312181230/pear/install-pear.php -d
/usr/local/php/lib/php/ -b /usr/local/php/bin/
/usr/src/php5-200312181230/pear/packages/*.tar
Tracing all script with Xdebug, seems that the last
function call is:
23.4601
At 07:20 PM 12/18/2003 +0100, Christian Schneider wrote:
Derick Rethans wrote:
It won't bork all scripts with a custom errorhandler if their default
action is to ignore core and other errors but only handle the ones they
should handle. I do agree that it should be mentioned in the changes
file thou
Derick Rethans wrote:
It won't bork all scripts with a custom errorhandler if their default
action is to ignore core and other errors but only handle the ones they
should handle. I do agree that it should be mentioned in the changes
file though.
On the other hand you have to be very careful (anothe
32 matches
Mail list logo