headers
Rob Richards | 1 Sep 2005 01:58

Re: [PHP-DEV] PHP 5.1

I would suggest bumping up the libxm2 minimum version to 2.6.8. Had 
forgotten about this until a recent bug, but 2.6.6 and 2.6.7 can cause 
memory corruption thats fixed in 2.6.8.

Rob

Zeev Suraski wrote:

> For those of you who submitted patches to 5.1 since RC1 - do you 
> believe that we need another RC or can we go ahead and roll 5.1 final 
> and run a sanity test for 24 hours?  I went over the patches, none of 
> them appears to be too dangerous, but if any of you thinks 
> differently, let me know.
>
> Zeev
>

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 1 comment |
headers
Steph | 1 Sep 2005 01:53
Favicon

Re: [PHP-DEV] PHP 6.0 Wishlist

> Let's please stop breaking things just because we find them
> aesthetically displeasing.

*hug*
 
> -adam

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 0 comments |
headers
steve | 1 Sep 2005 02:30
Picon

[PHP-DEV] Bugs in 5.0.5 and 5.1 RCs

OK, knowing *exactly* what is going on when there are lots of other
peoples code involved (a framework, ADODB, JPSpan, etc.) is tuff, but
here is what I think:

The lowdown: mysqli seems to be gone by the time the shutdown function
is called (the error being "Couldn't fetch mysqli"). That makes an
exception, and depending on whatever else is loaded, it will either
try to squelch the error or throw a new exception which leads to the
error at Unknown at line 0 bug.

At any rate, there are two problems:
1) That the newly thrown exception blows up into a fatal error that
doesn't list the file or line number.

2) mysqli is unloaded(!?) (or appears to be) before the the user's
shutdown function is called. This one is SERIOUS -- I use it to save
session data, etc. This then becomes impossible to do.

In the backtrace you'll notice that the function table (in fact, all
parameters, are, as Markus says, borked!) when going from
call_user_function() to call_user_function_ex() on the mysqli
extention.

#24 0x0823e95c in call_user_function_ex (function_table=0x1,
object_pp=0x1, function_name=0x1, retval_ptr_ptr=0x1, param_count=1,
params=0x1, no_separation=1, symbol_table=0x1)
   at /php-5.1.0RC1/Zend/zend_execute_API.c:571
#25 0x0823e998 in call_user_function (function_table=0xa0a2350,
object_pp=0x0, function_name=0xa43f80c, retval_ptr=0xbfe96ad0,
param_count=0, params=0xa448280)
(Continue reading)

Permalink | Reply | 2 comments |
headers
steve | 1 Sep 2005 03:44
Picon

[PHP-DEV] Some results: Moving to PHP5.1 and Apache 2.2 next year, need help

First off, I know I said I was going to try lighhtpd: the site I'm
testing this on has so many rewrite rules, I just didn't have enough
ambition...

That said, the end result is that I put Apache1/mod_php4 up against
Apache2/FastCGI/PHP4. Well, under real load both did about the same.
The Apache2 setup averaged a smaller "load average" as defined by top.
;) It also used more memory. More on that later. But overall, they
performed about the same.

The same, except that the Apache2 setup could leave KeepAlive turned
on. It's status also shows how many threads are in Keep-Alive and
Close states (with Apache1 would have shown the close state), which is
nice. It is still one thread to one connection pairing (unlike the
event mpm to be in apache2.2), but even so, that is much better one
user connection to one PHP process, IMHO.  I liked the snappiness of
the site much better so I went ahead and migrated it. Works great.

I've read where other people have put a small web farm behind a load
balancer and then load balanced them to a larger pool of PHP servers
with no webserver on those machines at all. I suppose that would work
well for sites that have a good mix of static and lots of dynamic
content. It would take some experience to figure out how to propery
manage that. Probably the next step for me to worry about for another
site -- one that is truly large but not really ready to go with
separate domains for images or akamai.

There are some downsides:

1. At least the way I have it setup, I have a fixed set of PHP
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andi Gutmans | 1 Sep 2005 05:14
Favicon

Re: [PHP-DEV] PHP 5.1

Rasmus,

please send an update what you think you can do on your side...
Thanks,

Andi

At 08:33 PM 8/30/2005, Wez Furlong wrote:
>http://bugs.php.net/search.php?cmd=display&status=Open&bug_type%5B%5D=PDO+related
>http://pecl.php.net/bugs/search.php?cmd=display&status=Open&package_name%5B%5D=PDO&package_name%5B%5D=PDO_FIREBIRD&package_name%5B%5D=PDO_MYSQL&package_name%5B%5D=PDO_OCI&package_name%5B%5D=PDO_ODBC&package_name%5B%5D=PDO_PGSQL&package_name%5B%5D=PDO_SQLITE
>
>They sound pretty straight-forward (although #33707 and #34233 sound a
>bit harder), so if you do have some resources to throw at them, I'd
>really appreciate it--I've just been too damned busy lately, and don't
>forsee having the time to sit down and get it done for a week or so.
>
>--Wez.
>
>On 8/30/05, Rasmus Lerdorf <rasmus <at> lerdorf.com> wrote:
> > Wez Furlong wrote:
> > > There's a bunch of open PDO bugs that need to be fixed before we go
> > > with 5.1 final.
> >
> > Do you have some sort of plan/timeline for these getting fixed?  Do you
> > need some help?  We can't wait indefinitely on PDO.  If you have a list
> > of outstanding issues I can throw some resources at it.
>
>--
>PHP Internals - PHP Runtime Development Mailing List
>To unsubscribe, visit: http://www.php.net/unsub.php
(Continue reading)

Permalink | Reply | 0 comments |
headers
Peter Brodersen | 1 Sep 2005 05:15
Picon

Re: [PHP-DEV] Re: glob to take array as an arg

On Wed, 31 Aug 2005 11:39:04 +1000, in php.internals kevin <at> oceania.net
(Kevin Waterson) wrote:

>> print_r(glob("*.{jpg,gif,tif,pdf,bmp,raw}",GLOB_BRACE));
>
>True, but not available to all. It is GNU.

You are right - I missed that win32 uses win32/glob.h

I think a better solution is just to create an emulation for
GLOB_BRACE. This is nothing new, GLOB_ONLYDIR is already emulated on
systems not using the GNU C library (where GLOB_EMULATE_ONLYDIR is
defined instead) since 4.3.3.

On one hand it would be nice with more cross-platform-compatibility.
Using local libraries might create incompatibility, forcing users to
make usage of PEAR libraries and such instead of native functions
(though File_Find, that has just reached stable for a 1.0.x-release,
could be an alternative).

On the other hand, more code would make require more maintenance. Not
that it seems like glob.h is that troublesome.

-- 
- Peter Brodersen

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ron Korving | 1 Sep 2005 07:11
Picon

Re: [PHP-DEV] Re: PHP 6.0 Wishlist

Hi,

> >> > 2) error reporting using exceptions.
> >> > I would like it if I could catch PHP-errors and take appropriate
action
> >> > (such as logging it to a database or whatever).
> >>
> >> You can already do that with 5.1 by adding three lines of code.
>
> > Sounds awesome.. is this documented (I don't mean the PHP manual)
anywhere?
> > I'm curious as to how this works.
>
> Look for slide 42 in talk 'SPL for the masses' here:
http://talks.somabo.de

Oh my god, I am so ashamed (hangs head between knees)... sorry.

> > I looked into the source, but I'm I couldn't quite grasp the inner
workings.
> > I promised myself to get into more actively "developing" in this area,
maybe
> > apply for a CVS account in time... but that's gonna take some time.
Where do
> > I see who maintains a certain extension?
>
>
> look into the EXTENSIONS file or in the head of any .h or .h file.
>
> marcus
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Coggeshall | 1 Sep 2005 09:01

Re: [PHP-DEV] PHP 6.0 Wishlist

Didn't say I thought it was going to happen, just that I rather take a
step "back" then a step "forward" if any movement at all was going to
happen.

John

On Wed, 2005-08-31 at 17:15 -0400, Adam Maccabee Trachtenberg wrote:
> Let's please stop breaking things just because we find them
> aesthetically displeasing.
> 
> -adam
> 
> On Wed, 31 Aug 2005, John Coggeshall wrote:
> 
> > So very -1 on anything introducing another way to print stuff. I am
> > however +1 on turning off everything but <?php from php.ini
> >
> > John
> >
> > On Wed, 2005-08-31 at 22:44 +0200, Edin Kadibasic wrote:
> > > Marcus Boerger wrote:
> > > > Hello Wez,
> > > >
> > > >   we could however drop '<%' support and introduce '<?php=' support.
> > >
> > > You'll have to pry '<%' from my cold, dead hands :)
> > >
> > > Edin
> > >
> >
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jani Taskinen | 1 Sep 2005 10:26
Picon
Picon
Favicon

Re: [PHP-DEV] PHP 5.1


     Done. All distros should have at least 2.6.8. Most have 2.6.16 or above..

     --Jani

On Wed, 31 Aug 2005, Rob Richards wrote:

> I would suggest bumping up the libxm2 minimum version to 2.6.8. Had forgotten 
> about this until a recent bug, but 2.6.6 and 2.6.7 can cause memory corruption 
> thats fixed in 2.6.8.
>
> Rob
>
> Zeev Suraski wrote:
>
>> For those of you who submitted patches to 5.1 since RC1 - do you believe 
>> that we need another RC or can we go ahead and roll 5.1 final and run a 
>> sanity test for 24 hours?  I went over the patches, none of them appears to 
>> be too dangerous, but if any of you thinks differently, let me know.
>> 
>> Zeev
>> 
>
>

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
(Continue reading)

Permalink | Reply | 0 comments |
headers
Derick Rethans | 1 Sep 2005 10:31
Picon
Gravatar

Re: [PHP-DEV] PHP 5.1

On Wed, 31 Aug 2005, Derick Rethans wrote:

> On Tue, 30 Aug 2005, Zeev Suraski wrote:
> 
> > For those of you who submitted patches to 5.1 since RC1 - do you believe that
> > we need another RC or can we go ahead and roll 5.1 final and run a sanity test
> > for 24 hours?  I went over the patches, none of them appears to be too
> > dangerous, but if any of you thinks differently, let me know.
> 
> Should I also commit:
> http://files.derickrethans.nl/patches/e_recoverable_error-php-5.1-20050826.diff.txt
> ?

Should I assume that if nobody replies, there are no objections?

Derick

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 2 comments |

Gmane