Just checked out and compiled.
make install-pear-packages is OK for me now.
How about the others to it was segfaulting???
Eduardo R. Maciel
__
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
--
PHP Internals - PHP Runti
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
At 10:17 PM 12/18/2003 +0100, Christian Schneider wrote:
I agree wholeheartedly, especially since one can set reporting to E_ALL and
then ignore whatever one likes but with the way it is now there is no way
of not being called for everything.
If you want I could provide patches which
a) fix the
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
Hi,
as I wrote in my initial post: Even changing the paramters for
pear/install-pear.php "helps" and I am not able to create a simpler
script reproducing the crash. But meanwhile I've found the time when it
broke:
zend_execute.c,v 1.565 2003/12/14 16:09:07 still works but
zend_execute.c,v 1.566
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
Andi Gutmans wrote:
Yeah this is a known bug and will have to be fixed in RC1. It's not a
showstopper for B3.
Yes, this bug has indeed nothing to do with B3. I just though that PHP5
would maybe be the time to make set_error_handler finally usable.
In any case, I do think that the custom error ha
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
Greg:
On Thu, Dec 18, 2003 at 12:48:01PM -0500, Greg Beaver wrote:
>
> Thanks for the catch Dan, that fixes it.
But your fix uses the E_STRICT constant, which of course doesn't exist in
PHP 4, so an undefined constant notice gets produced.
I'm wondering why there's even a custom error handler
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
Any chance you can dissect it to the smallest piece of code that still
produces the crash?
At 14:46 18/12/2003, Pierre-Alain Joye wrote:
On Thu, 18 Dec 2003 12:43:03 +0100
Pierre-Alain Joye <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm trying to see why $ make install-pear-packages segfaults with
>
On Thu, 18 Dec 2003, Greg Beaver wrote:
> At the least, this needs to be added to the thin-changes file, as it
> will bork any script that uses a custom error handler and has PHP 4 objects.
It won't bork all scripts with a custom errorhandler if their default
action is to ignore core and other er
On Thursday 18 December 2003 18.25, Christian Schneider wrote:
> Daniel Convissor wrote:
> > It's the custom error handler in pearcmd.php. PHP doesn't pay attention
> > to any error_reporting() settings when a custom error handler is
> > established. Then, error_handler() doesn't account for the
At the least, this needs to be added to the thin-changes file, as it
will bork any script that uses a custom error handler and has PHP 4 objects.
Thanks for the catch Dan, that fixes it.
Greg
Christian Schneider wrote:
Daniel Convissor wrote:
It's the custom error handler in pearcmd.php. PHP
On Thu, 18 Dec 2003, Christian Schneider wrote:
> Daniel Convissor wrote:
> > It's the custom error handler in pearcmd.php. PHP doesn't pay attention
> > to any error_reporting() settings when a custom error handler is
> > established. Then, error_handler() doesn't account for the new warning
>
Personally, I both like and dislike this behavior. I like it for debugging
purposes, since it allows me full control over whether I ignore
error_reporting level or perhaps just log disabled levels instead of
displaying them, etc. On the other hand, there is a minor performance issue,
but if you w
Daniel Convissor wrote:
It's the custom error handler in pearcmd.php. PHP doesn't pay attention
to any error_reporting() settings when a custom error handler is
established. Then, error_handler() doesn't account for the new warning
level.
Is it just me or is this undesired behaviour? I noticed th
Hi:
On Thu, Dec 18, 2003 at 12:08:09PM -0500, Greg Beaver wrote:
> Unless it is possible to turn on E_STRICT without using the
> error_reporting() function
It's the custom error handler in pearcmd.php. PHP doesn't pay attention
to any error_reporting() settings when a custom error handler is
es
Unless it is possible to turn on E_STRICT without using the
error_reporting() function, then this is not true - there is only 1
error_reporting() in all of the .php files that make up the PEAR core,
try grep if you don't believe me.
Greg
Daniel Convissor wrote:
On Thu, Dec 18, 2003 at 11:44:27
On Thu, Dec 18, 2003 at 04:38:28PM -, Wez Furlong wrote:
> If you paid attention to the list, and read the README,
> you would have discovered that I'd already stated this.
It wasn't mentioned on the list. Yes, it's now in the readme file, but I
was working on an old release that didn't have
On Thu, Dec 18, 2003 at 11:44:27AM -0500, Greg Beaver wrote:
> I wonder if E_STRICT is on no matter what in head?
It's not. Something in the pear install scripts is turning it on.
--Dan
--
FREE scripts that make web and database programming easier
http://www.analysisandsolutio
The only call to error_reporting() is in pearcmd.php:
error_reporting(E_ALL & ~E_NOTICE);
I added a var_dump(error_reporting()); and got 2039 out, as expected,
but I am still getting E_STRICT warnings galore. I wonder if E_STRICT
is on no matter what in head? I added & ~E_STRICT (which of cou
If you paid attention to the list, and read the README,
you would have discovered that I'd already stated this.
Downloading the PSDK is useful if you only have VC6 and want
an up-to-date build environment.
mscoree.h is part of the .Net SDK.
--Wez.
> > You also need the Microsoft build tools (cl
On Tue, Dec 02, 2003 at 11:40:18PM -, Wez Furlong wrote:
> You also need the Microsoft build tools (cl.exe, link.exe and nmake.exe).
> These are freely available as part of the Platform SDK, but also
> come with VC++/Visual Studio.
Folks, don't waste your time downloading and installing the P
On Thu, 18 Dec 2003 14:44:29 +0100 (CET)
Derick Rethans <[EMAIL PROTECTED]> wrote:
> Guesso... can you try to run it in valgrind, it should show all memory
> overruns etc..
Already done, no overuns, and obviously non freed mem after the crash ;)
Important note (dunno why I did not say that befo
On Thu, 18 Dec 2003, Daniel Convissor wrote:
> Hi Pierre:
>
> On Thu, Dec 18, 2003 at 12:43:03PM +0100, Pierre-Alain Joye wrote:
> >
> > I got new messages (which where not displayed before):
> > : var: Deprecated. Please use the public/private/protected modifiers in
> > XXX.php on line XX
>
> I n
Hi Pierre:
On Thu, Dec 18, 2003 at 12:43:03PM +0100, Pierre-Alain Joye wrote:
>
> I got new messages (which where not displayed before):
> : var: Deprecated. Please use the public/private/protected modifiers in
> XXX.php on line XX
I noticed the same thing. The new E_STRICT reporting level prod
On Thu, 18 Dec 2003, Pierre-Alain Joye wrote:
> On Thu, 18 Dec 2003 13:50:10 +0100 (CET)
> Derick Rethans <[EMAIL PROTECTED]> wrote:
>
> > On Thu, 18 Dec 2003, Pierre-Alain Joye wrote:
> >
> > > Ok segfault is on line pear/PEAR/Registry.php line 345.
> > >
> > > This is a call to unserialize. I do
Hello Pierre-Alain,
Thursday, December 18, 2003, 12:43:03 PM, you wrote:
> Hello,
> I'm trying to see why $ make install-pear-packages segfaults with HEAD.
> I hope I'll commit the fixes today. I suspect references problem...
> I got new messages (which where not displayed before):
> : var: Dep
On Thu, 18 Dec 2003 13:50:10 +0100 (CET)
Derick Rethans <[EMAIL PROTECTED]> wrote:
> On Thu, 18 Dec 2003, Pierre-Alain Joye wrote:
>
> > Ok segfault is on line pear/PEAR/Registry.php line 345.
> >
> > This is a call to unserialize. I do not know yet why it fails. Maybe
> > (again) the serialized
On Thu, 18 Dec 2003, Pierre-Alain Joye wrote:
> Ok segfault is on line pear/PEAR/Registry.php line 345.
>
> This is a call to unserialize. I do not know yet why it fails. Maybe
> (again) the serialized data is corrupted. Anyway unserialize should
> ""never"" segfault.
Can you put the datafile + s
On Thu, 18 Dec 2003 12:43:03 +0100
Pierre-Alain Joye <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm trying to see why $ make install-pear-packages segfaults with
> HEAD. I hope I'll commit the fixes today. I suspect references
> problem...
>
> I got new messages (which where not displayed before):
Yeah go ahead if they are well tested. I want to see what's up with the
PEAR install crash.
Andi
At 11:10 AM 12/18/2003 +, Wez Furlong wrote:
Hey Andi,
I have some fixes for:
com_dotnet: correctly manage lifetime of .Net runtime host
for long-lived servers (eg: anything except cgi and cli)
Hello,
I'm trying to see why $ make install-pear-packages segfaults with HEAD.
I hope I'll commit the fixes today. I suspect references problem...
I got new messages (which where not displayed before):
: var: Deprecated. Please use the public/private/protected modifiers in
XXX.php on line XX
Hav
Committed.
--Wez.
> com_dotnet: correctly manage lifetime of .Net runtime host
> for long-lived servers (eg: anything except cgi and cli)
> so that .net objects can be created beyond the first
> request per process.
>
> tidy: fix ZTS build
>
> apache: fix build under win32 when you have IPV6 ca
Hey Andi,
I have some fixes for:
com_dotnet: correctly manage lifetime of .Net runtime host
for long-lived servers (eg: anything except cgi and cli)
so that .net objects can be created beyond the first
request per process.
tidy: fix ZTS build
apache: fix build under win32 when you have IPV6 cap
On Thu, 18 Dec 2003, Derick Rethans wrote:
> On Thu, 18 Dec 2003, Derick Rethans wrote:
>
> > On Thu, 18 Dec 2003, Andi Gutmans wrote:
> >
> > > Is it OK with latest HEAD? I saw Rasmus commited a patch.
> >
> > Yes, works in HEAD now.
>
> But now I get a link error:
>
> gcc: /usr/lib/libtidy.so: N
On Thu, 18 Dec 2003, Derick Rethans wrote:
> On Thu, 18 Dec 2003, Andi Gutmans wrote:
>
> > Is it OK with latest HEAD? I saw Rasmus commited a patch.
>
> Yes, works in HEAD now.
But now I get a link error:
gcc: /usr/lib/libtidy.so: No such file or directory
[EMAIL PROTECTED]:/dat/dev/php/php-5.
On Thu, 18 Dec 2003, Andi Gutmans wrote:
> I really wouldn't like B3 to crash on install-pear-packages.
> Can you guys take a closer look and see what the problem is?
Ill have a look if I can reproduce it.
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: ht
On Thu, 18 Dec 2003, Andi Gutmans wrote:
> Is it OK with latest HEAD? I saw Rasmus commited a patch.
Yes, works in HEAD now.
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I really wouldn't like B3 to crash on install-pear-packages.
Can you guys take a closer look and see what the problem is?
Andi
At 08:37 AM 12/18/2003 +0100, Markus Fischer wrote:
Just want to add that I was seeing this segfaults too over the last
few days; merely when NOT installing from a
Just want to add that I was seeing this segfaults too over the last
few days; merely when NOT installing from a clean built cvs (e.g.
running configure a second time); also always crashed in
install-pear-packages when it did crash. Didn't pay much attention
because I thought tha
On Thu, 18 Dec 2003 08:13:13 +0100
Markus Fischer <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 17, 2003 at 08:00:06PM +0300, Antony Dovgal wrote :
> > ocifetchinto -- this is a special case. I'd prefer to make 3 functions
> > instead of it: oci_fetch_row, oci_fetch_array & oci_fetch_assoc
>
> Ju
On Wed, Dec 17, 2003 at 08:00:06PM +0300, Antony Dovgal wrote :
> ocifetchinto -- this is a special case. I'd prefer to make 3 functions
> instead of it: oci_fetch_row, oci_fetch_array & oci_fetch_assoc
Just curious; there are other extension which provide
*fetch_object() too. Did you lea
I am Croatian studying computer science in the United States. Presently, I have been 4
years in the USA; so I believe I would a great person to translate PHP documentation
in Croatian. Not only I would help Croatian webdevelopers learn PHP quicker, but I
would make more Croatian webdevelopers in
72 matches
Mail list logo
