[PHP-DEV] Re: [PHP-CVS] cvs: php4 / run-tests.php
I thought we discussed that any error/warning message MUST cause a test to fail. If you look at the diffs you will see that. And that we do not use logging but direct displaying for that. And again when special tests fail because a warning is emitted you should either use --INI-- to disable messages for that single test only or even better you should use --EXPECTF-- to detect the expected messages. The other thing you removed is error_log: I do not think this should be removed since the idea was to have all error related ini settings beeing the same. So what ever you do please enable one mechanism to display those errors and warnings. regards marcus At 19:48 28.10.2002, Ilia Alshanetsky wrote: iliaa Mon Oct 28 13:48:07 2002 EDT Modified files: /php4 run-tests.php Log: This patch addresses the bogus test failures due to error logging/reporting confusion. Index: php4/run-tests.php diff -u php4/run-tests.php:1.97 php4/run-tests.php:1.98 --- php4/run-tests.php:1.97 Mon Oct 28 13:21:09 2002 +++ php4/run-tests.php Mon Oct 28 13:48:07 2002 -490,11 +490,10 open_basedir=, disable_functions=, error_reporting=2047, - display_errors=1, + display_errors=0, log_errors=0, html_errors=0, track_errors=1, - error_log=, report_memleaks=1, docref_root=/phpmanual/, docref_ext=.html, -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] I hope this is the last email about this :)
Derick Rethans wrote: On Tue, 29 Oct 2002, Yasuo Ohgaki wrote: Zeev Suraski wrote: Please revert. There is no need. Derick has been changed it w/o discussion. Nice joke :) Don't you forget I've posted I'll change it? I get reply only from you, though. Old code was bogus as everyone knew now. Your patch made impossible to turn off implicit flushing at all. I know you've modified code at very late stage of discussion to fix it, even if I've mentioned the problem number of times. Nice joke to you :) -- Yasuo Ohgaki -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: setting PHP_INI_SYSTEM config. variables in VHost sections (bug20009)
Matus Fantomas Uhlar wrote: (B Therefore I propose a change: (B (B PHP_INI_SYSTEM variables should be allowed to change by admin - in (B system-wide php.ini or httpd.conf, no matter if it's VHost or not. (B (BI've never tried to use php_value/php_admin_value/php_flag/php_admin_flag (Bin global httpd.conf context. Does it work with Apache1.x SAPI? (B (BHave you tried php_admin_vlaue/php_admin_flag? (B(PHP_INI_ALL directives can be modified in script at least under 4.3.0-dev, (Bthough) (B (BThere may be things that are behaving differently from Apache SAPI. (BPlease report it bug, see if Apache2 SAPI can be made work like (BApache SAPI. (Search bug db first, 1 bug/report, please) (B (B (B PHP_INI_PERDIR would be then made useless and .htaccess things can be (B checked with PHP_INI_USER. (B (B (BI probably don't understand this line correctly. (B (B-- (BYasuo Ohgaki (B (B (B-- (BPHP Development Mailing List http://www.php.net/ (BTo unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] I hope this is the last email about this :)
On Tue, 29 Oct 2002, Yasuo Ohgaki wrote: Derick Rethans wrote: On Tue, 29 Oct 2002, Yasuo Ohgaki wrote: There is no need. Derick has been changed it w/o discussion. Nice joke :) Don't you forget I've posted I'll change it? I get reply only from you, though. Old code was bogus as everyone knew now. Bogus? *sigh*... no more comments on this. Your patch made impossible to turn off implicit flushing at all. I know you've modified code at very late stage of discussion to fix it, even if I've mentioned the problem number of times. That is not even true, you always could disable that hardcoded setting by passing the -d option to the Command Line Interface. Derick -- --- Derick Rethans http://derickrethans.nl/ JDI Media Solutions --[ if you hold a unix shell to your ear, do you hear the c? ]- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] I hope this is the last email about this :)
Derick Rethans wrote: Your patch made impossible to turn off implicit flushing at all. I know you've modified code at very late stage of discussion to fix it, even if I've mentioned the problem number of times. That is not even true, you always could disable that hardcoded setting by passing the -d option to the Command Line Interface. True, but everyone has to wait until everyone installs php/cli to standard location, such as /usr/bin/php, to have control behavior of php scripts for distributing :) I have no idea about Windows ;) -- Yasuo Ohgaki -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-CVS] Discuss on php-dev, not on php-cvs please
That would be ideal :) On Tue, 29 Oct 2002, Derick Rethans wrote: On Tue, 29 Oct 2002, Wez Furlong wrote: If you need to comment on a commit, can you please change the To/Cc line from php-cvs to php-dev. I think we can instruct the listmanager to set a Reply-To header instead, would that be a nice idea? -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-CVS] Discuss on php-dev, not on php-cvs please
Even stricter and be sure, prevent post from users like php-bugs? -- Yasuo Ohgaki Wez Furlong wrote: That would be ideal :) On Tue, 29 Oct 2002, Derick Rethans wrote: On Tue, 29 Oct 2002, Wez Furlong wrote: If you need to comment on a commit, can you please change the To/Cc line from php-cvs to php-dev. I think we can instruct the listmanager to set a Reply-To header instead, would that be a nice idea? -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PEAR-DEV] Go-Pear goes Web!
Hello! I've been trying to use the go-pear WebInstaller with some lack of success. On Win2k running php 4.2.2 I get the folowing: Downloading package: PEAR.ok Downloading package: Archive_Tar..ok Downloading package: Console_Getoptok Downloading package: XML_RPC..ok Downloading package: Pagerok Downloading package: HTML_Template_ITok Downloading package: Net_UserAgent_Detectok Downloading package: PEAR_Frontend_Webok Bootstrapping: PEAR...ok Bootstrapping: Archive_Tarok Bootstrapping: Console_Getopt.ok Downloading package: DB...ok Downloading package: Net_Socket...ok Downloading package: Net_SMTP.ok Downloading package: Mail.ok Downloading package: XML_Parser...ok Extracting installer.. Invalid checksum : 40057 calculated, 0 expected And then I get some unlink() failed messages. Besides this, it looks like a really great little thing! Btw, the action in the Install form does not work in Opera (v 6.04). Using ?= $_SERVER['PHP_SELF'] ? instead of ?php basename(__FILE__);? does the job. If I'm missing out on something, please - let me know! :-) Regards, Nils-Fredrik G. Kaland - Original Message - From: Christian Dickmann [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, October 26, 2002 7:12 PM Subject: [PEAR-DEV] Go-Pear goes Web! Hi, PEAR wants YOU to test something new! I changed go-pear to be accessable through browsers to install PEAR_Frontend_Web (Web Installer). How to test/install? 1. Download http://dickmann.homeunix.org/pear/pearweb/public_html/go-pear.php 2. Put it somewhere reachable though HTTP 3. Access it with your favorite browser 4. Install it ... 5. Feel happy to see the Web Installer A diff to current go-pear is also available, but the great amount of changes makes it unreadable IMHO ... http://dickmann.homeunix.org/pear/pearweb/public_html/go-pear.diff.txt Christian Dickmann PS: What do you think about bundling the images with go-pear by including them base64 encoded ;) -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-CVS] Some NetWare files are not getting committed.
This worked fine! Thanks for this input. - Ananth. Edin Kadribasic [EMAIL PROTECTED] 10/29/02 03:18PM Adding folder is not enough. You need to add the files within the folder as well. Hope this helps, Edin - Original Message - From: Ananth Kesari [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, October 29, 2002 10:32 AM Subject: Re: [PHP-CVS] Some NetWare files are not getting committed. Thanks for the inputs. Still I do not get NetWare folder. I did the following: 1. In the .cvsrc file: cvs -z3 update -d checkout -P diff -u I did: cvs add -m NetWare related files. netware The netware folder had all the files within it with a sub-directory also by name sys. I got a list of all these files and was told that these were added. Then I went into the sys sub-directory and added it also with the files within it. It told me that those files were added too. Then I did: cvs commit -m NetWare related files. netware It said: Examining netware Examining netware\sys Then it came out without doing anything. Then when I did: cvs co -r PHP_4_2_0 php4, I still DON'T get the netware folder. 2. I tried all the above with the following entries in the .cvsrc file: cvs -z3 update -d diff -u Still the same result. I do not get netware folder when I do a check-out. For your information, NetWare and sys folders were not empty when I first did the add and commit last Friday and also yesterday. Can you let me know what to do now? Thanks, Ananth. Melvyn Sopacua [EMAIL PROTECTED] 10/28/02 08:55PM At 15:49 28-10-2002, Ananth Kesari wrote: But I need to add a folder by name, netware with some NetWare specific files within it. These are NOT getting committed. If I add it gets added. I once committed on Thursday. Now, if I commit, it verifies and does nothing indicating that it is already committed. But if I check-out the 4.2 project, I do not get the netware folder. Can anyone tell me what's wrong? I am a beginner to this CVS process and so I may be missing something even simple or obvious. Since you probably have update -d -P in your ~/.cvsrc like you should, the directory won't show up, untill you commit files in them. Remove the -P option from your ~/.cvsrc directory temporarily to get the netware directory back. -P means prune, which deletes empty dirs -d means create new directory that's cause the conflict. HTH With kind regards, Melvyn Sopacua ?php include(not_reflecting_employers_views.txt); ? -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-CVS] Discuss on php-dev, not on php-cvs please
On Tue, 29 Oct 2002, Yasuo Ohgaki wrote: Even stricter and be sure, prevent post from users like php-bugs? -- Yasuo Ohgaki Wez Furlong wrote: That would be ideal :) On Tue, 29 Oct 2002, Derick Rethans wrote: On Tue, 29 Oct 2002, Wez Furlong wrote: If you need to comment on a commit, can you please change the To/Cc line from php-cvs to php-dev. I think we can instruct the listmanager to set a Reply-To header instead, would that be a nice idea? -1000. Just leave it alone, it's fine as it is. --Jani -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installation instructions
The aspect people complaining about is more a version thingie, e.g. they try to set up php 4.2.3 with apache 2.0.43 and this could not succeed. Is it really necessary to document that apache 2.03x works only with php 4.2.x1, php4.2.x2 and apache 2.04x only with php4.2y1 or php4.2.y2? It should be clearly mentioned, that the support for apache2 isn't production stable ;-) I think, it would be nice to add information to one place, the documentation about Apache 2 support. 1. It's not production ready 2. If someone want to set it up, how to do it (Linux, Windows) 3. What PHP versions work with what Apache 2 versions For this information it would be nice if someone from the devs could give a short view about. PHP-Version: Apache version supported: 4.2.0 started ?? 4.2.1 ?? 4.2.2 ?? 4.2.3 2.0.3x or 2.0.4x snap build2.0.43 I am also satified if someone could tell me, where to find this info by mayself :-) 4. It should be noted, that Apache 1 support is continued ;) O.K. if I'll find the time I'all add some initial docs about. Also a point to consider is the name of the correct cgi executable for win: in 4.2.3 it's php.exe the cli-build names php-cli.exe. In the 4.3.0-dev the cli names php.exe and the cgi-version php-cgi.exe. I don't know why the names changed, maybe to confuse the people once more and to give some work for the doc-folks ;-) Doh, it would be nice to stick to some final names ;) Could someone of the devs give a hint, please? NOTE: cca. 80% of the user notes on the Apache setup page deals with Apache 2 installation. We should add verified info to the docs, and delete those notes. There are many sites offering a php4apache2.dll to download. These can harm our users, as they can contain any vulnerable code, which our users download, just because there is no official support/documentation for Apache... http://www.php.net/manual/en/install.apache.php Please keep this in mind, o.k. convinced :-) Friedhelm -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installation instructions
At 08:43 29-10-2002, Gabor Hojtsy wrote: The aspect people complaining about is more a version thingie, e.g. they try to set up php 4.2.3 with apache 2.0.43 and this could not succeed. Is it really necessary to document that apache 2.03x works only with php 4.2.x1, php4.2.x2 and apache 2.04x only with php4.2y1 or php4.2.y2? It should be clearly mentioned, that the support for apache2 isn't production stable ;-) I think, it would be nice to add information to one place, the documentation about Apache 2 support. 1. It's not production ready Ah yes - but that will contradict greatly, to the best version yet marketing trick the Apache Group is advertising on their front page. We can mention it to users, in the bug db etc. But officially documenting, that Apache 2 is really a beta product, doesn't really express consistency, between the family. I'm aware that this is not a technical reason not to do this, I'm just pointing out how this can be perceived. With kind regards, Melvyn Sopacua ?php include(not_reflecting_employers_views.txt); ? -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installation instructions
On Tue, 29 Oct 2002, Melvyn Sopacua wrote: At 08:43 29-10-2002, Gabor Hojtsy wrote: I think, it would be nice to add information to one place, the documentation about Apache 2 support. 1. It's not production ready Ah yes - but that will contradict greatly, to the best version yet marketing trick the Apache Group is advertising on their front page. We can mention it to users, in the bug db etc. But officially documenting, that Apache 2 is really a beta product, doesn't really express consistency, between the family. I'm aware that this is not a technical reason not to do this, I'm just pointing out how this can be perceived. We can't change the fact that they simply lie about it. But wording it like Apache and PHP are not to be used in production environments should not produce flames from the apache people I think :) Derick -- --- Derick Rethans http://derickrethans.nl/ JDI Media Solutions --[ if you hold a unix shell to your ear, do you hear the c? ]- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installation instructions
Hallo Melvyn, Tuesday, October 29, 2002, 9:55:31 AM, you wrote: At 08:43 29-10-2002, Gabor Hojtsy wrote: The aspect people complaining about is more a version thingie, e.g. they try to set up php 4.2.3 with apache 2.0.43 and this could not succeed. Is it really necessary to document that apache 2.03x works only with php 4.2.x1, php4.2.x2 and apache 2.04x only with php4.2y1 or php4.2.y2? It should be clearly mentioned, that the support for apache2 isn't production stable ;-) I think, it would be nice to add information to one place, the documentation about Apache 2 support. 1. It's not production ready Ah yes - but that will contradict greatly, to the best version yet marketing trick the Apache Group is advertising on their front page. We can mention it to users, in the bug db etc. But officially documenting, that Apache 2 is really a beta product, doesn't really express consistency, between the family. I thought it more from another point of view: the support for apache2 in php is not production stable ,e.g. the sapi in php :-) Maybe this is due to the fact (?) that apache2 is still beta (I really don't know) but form the php-side point of view, php-versions are not production stable in conjunction with apache2. As Derick said, I don't think this will hurt someone of the apachegroup. [...] but besides this, it would be kind, if just someone could provide some infos from the php-side, like the *.exe names one windows ;-) Friedhelm -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PEAR-DEV] Go-Pear goes Web!
Hello! I've been trying to use the go-pear WebInstaller with some lack of success. On Win2k running php 4.2.2 I get the folowing: Downloading package: PEAR.ok Downloading package: Archive_Tar..ok Downloading package: Console_Getoptok Downloading package: XML_RPC..ok Downloading package: Pagerok Downloading package: HTML_Template_ITok Downloading package: Net_UserAgent_Detectok Downloading package: PEAR_Frontend_Webok Bootstrapping: PEAR...ok Bootstrapping: Archive_Tarok Bootstrapping: Console_Getopt.ok Downloading package: DB...ok Downloading package: Net_Socket...ok Downloading package: Net_SMTP.ok Downloading package: Mail.ok Downloading package: XML_Parser...ok Extracting installer.. Invalid checksum : 40057 calculated, 0 expected And then I get some unlink() failed messages. Besides this, it looks like a really great little thing! Btw, the action in the Install form does not work in Opera (v 6.04). Using ?= $_SERVER['PHP_SELF'] ? instead of ?php basename(__FILE__);? does the job. If I'm missing out on something, please - let me know! :-) Regards, Nils-Fredrik G. Kaland - Original Message - From: Christian Dickmann [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, October 26, 2002 7:12 PM Subject: [PEAR-DEV] Go-Pear goes Web! Hi, PEAR wants YOU to test something new! I changed go-pear to be accessable through browsers to install PEAR_Frontend_Web (Web Installer). How to test/install? 1. Download http://dickmann.homeunix.org/pear/pearweb/public_html/go-pear.php 2. Put it somewhere reachable though HTTP 3. Access it with your favorite browser 4. Install it ... 5. Feel happy to see the Web Installer A diff to current go-pear is also available, but the great amount of changes makes it unreadable IMHO ... http://dickmann.homeunix.org/pear/pearweb/public_html/go-pear.diff.txt Christian Dickmann PS: What do you think about bundling the images with go-pear by including them base64 encoded ;) -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] /tests/strings/003.phpt (htmlentities test)
Hi, I think the test case /tests/strings/003.phpt should be placed in /ext/standard/tests/strings and renamed as htmlentities.phpt . Are there any objections? Moriyoshi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] error_prepend_string error_append_string
Why use error_prepend_string error_append_string OnUndateStringUnempty? Shouldn`t they use OnUpdateString instead what is wanted in run-tests.php? marcus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] /tests/strings/003.phpt (htmlentities test)
Mybe you can also remove --GET-- and --POST-- and add --SKIPIF-- for setlocale() failure and missing --INI--. I guess you know best which settings affect this test. marcus At 15:12 29.10.2002, Moriyoshi Koizumi wrote: Hi, I think the test case /tests/strings/003.phpt should be placed in /ext/standard/tests/strings and renamed as htmlentities.phpt . Are there any objections? Moriyoshi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard/tests/file userstreams.phpt
On 10/29/02, Marcus B?rger [EMAIL PROTECTED] wrote: -Use // instead of /* ... */ comments Why? #this test fails for me. Very weired... You changed the test. Why not ask me first about it failing? --Wez. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard/tests/file userstreams.phpt
I started to work on that issue. My first attempt was to check where and why the test failed. I used the comment modification because it seems the test fails due to some internal failure. The reason i did not ask you before was that i considered my changes a kind of whitespace change so that any further change can easily be seen. The question i would like to ask now we already talk about this is: When i comment out everythink starting at ob_start() i get some output. If not (original) then i don't get any output. What is weired is that when i use any print/echo statement after ob_end_xxx() nothing is printed... The length of the lyrics added by me was only to test whether or not that part of the script works. marcus At 15:25 29.10.2002, Wez Furlong wrote: On 10/29/02, Marcus B?rger [EMAIL PROTECTED] wrote: -Use // instead of /* ... */ comments Why? #this test fails for me. Very weired... You changed the test. Why not ask me first about it failing? --Wez. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] setting PHP_INI_SYSTEM config. variables in VHostsections (bug 20009)
It should work fine, as long as you use the php_admin directives. At 21:50 20/10/2002, Matus fantomas Uhlar wrote: Hello, I found out that it is not possible with current php stable version (4.2.3) to define some configuration variables per virtual host - e.g. upload_tmp_dir. The upload_tmp_dir is masked ad PHP_INI_SYSTEM which allows changing php_upload_dir in php.ini or in httpd's main config - not in VHost config, which makes me unable to use different directories for each virtual web. I think that is very bad. The definition of PHP_INI_PERDIR allows changing variables in VHost sections or in .htaccess files. I don't understand this - users are usually able to configure .htaccess, which would allow them to overwrite settings in VHost section of httpd's config. I work with Apache, and with other http servers the situation can be different (any way I would wonder as long this is a policy-problem, not implementation problem). Therefore I propose a change: PHP_INI_SYSTEM variables should be allowed to change by admin - in system-wide php.ini or httpd.conf, no matter if it's VHost or not. PHP_INI_PERDIR would be then made useless and .htaccess things can be checked with PHP_INI_USER. -- Matus fantomas Uhlar, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I don't wish to receive spam to this address. Varovanie: Nezelam si na tuto adresu dostavat akukolvek reklamnu postu. Christian Science Programming: Let God Debug It!. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RFC: run-tests.php errors/warnings
I think we need to discuss the behaviour of run-tests.php according too error/warning handling a bit. First question (let me know if i am wrong): Any error/warning/ notice in a test result is either expected or a real error. To make that clear: Yes some tests failed after i made those visible but then i fixed the real problem and now there are no more warnings. Solution: Enable error reporting for any error/warning/notice etc. in run-tests.php and use the following where necessary a) Disable messages in --INI-- section of a test. When notices are expected E_ALL ~ E_NOTICE can be set as error_reporting=2039 b) Use in conjunction with $php_errormsg. --INI-- track_errors=1 display_erros=1 log_errors=0 --FILE-- erroneous_function_call(); echo $php_errormsg\n; --EXPECT-- Error message generated by error_prepend_string error_append_string c) Magically add echo $php_errormsg; after each --FILE-- section in run-tests.php But this is already condidered a baddirty solution. So my RFC is to use the following overwrites in run-test.phpt: error_reporting=2047 display_errors=1 log_errors=0 html_errors=0 track_errors=1 report_memleaks=1 docref_root=/phpmanual/ docref_ext=.html error_log= error_prepend_string= error_append_string= auto_append_file= auto_prepend_file= Remark 1: auto_append_file= auto_prepend_file= currently do not work but that is another thread. Remark 2: We could instead use the log_errors and direct them to the output with the following changes to above settings: display_errors=0 log_errors=1 The output would be nicer but when we go to test other sapis than CGI/CLI this won't work anymore. marcus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard/tests/file userstreams.phpt
Lets stick to C comments, as those are the preference listed in coding standards (and C++ style comments are really only intended for single line out-commenting anyhow). The test works fine here; it relies on output buffering working correctly; when the test passes you see only the expected output. If it fails, you see a trace of the seek offsets and expected positioning etc. etc. The failure of the test for you, and also the strange behaviour when changing the ob_xxx calls points a finger at the output buffer layer. Lets just make it a point to discuss something before changing someone elses code: comments and coding styles are often a touchy subject with a lot of developers (I'm normally fine with it, but it seemed pointless in this case, and against our general coding standards.) --Wez. On 10/29/02, Marcus Börger [EMAIL PROTECTED] wrote: I started to work on that issue. My first attempt was to check where and why the test failed. I used the comment modification because it seems the test fails due to some internal failure. The reason i did not ask you before was that i considered my changes a kind of whitespace change so that any further change can easily be seen. The question i would like to ask now we already talk about this is: When i comment out everythink starting at ob_start() i get some output. If not (original) then i don't get any output. What is weired is that when i use any print/echo statement after ob_end_xxx() nothing is printed... The length of the lyrics added by me was only to test whether or not that part of the script works. marcus At 15:25 29.10.2002, Wez Furlong wrote: On 10/29/02, Marcus B?rger [EMAIL PROTECTED] wrote: -Use // instead of /* ... */ comments Why? #this test fails for me. Very weired... You changed the test. Why not ask me first about it failing? --Wez. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RFC: run-tests.php errors/warnings
On October 29, 2002 09:52 am, Marcus Boerger wrote: I think we need to discuss the behaviour of run-tests.php according too error/warning handling a bit. First question (let me know if i am wrong): Any error/warning/ notice in a test result is either expected or a real error. Agreed, however in 99% of the cases the data which is being outputted is what matters. As long as it is the same data as the one we expect, all the warnings/notices are irrelevant, imho. That said, ideally the tests should not cause warnings/notices, unless of course, the purpose of the test is to see if a warning/notice message will be generated. In the event a needed warning is generated, the track_errors $php_errormsg facility should be used to display the error (we already enable tracking of errors by default). Adding to block the errors is not a good approach imho, the warning should be displayed and accounted for in the expected output. Remark 1: auto_append_file= auto_prepend_file= currently do not work but that is another thread. Seems to work just fine here. Remark 2: We could instead use the log_errors and direct them to the output with the following changes to above settings: display_errors=0 log_errors=1 The output would be nicer but when we go to test other sapis than CGI/CLI this won't work anymore. The tests can only be performed using the cgi/cli sapis since they require a command line PHP binary. So, this is a non-issue. If we must display error messages then I would prefer using display_errors=1 instead of log_errors=1. Ilia -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RFC: run-tests.php errors/warnings
On Tue, 29 Oct 2002, Ilia A. wrote: On October 29, 2002 09:52 am, Marcus Boerger wrote: Remark 2: We could instead use the log_errors and direct them to the output with the following changes to above settings: display_errors=0 log_errors=1 The output would be nicer but when we go to test other sapis than CGI/CLI this won't work anymore. The tests can only be performed using the cgi/cli sapis since they require a command line PHP binary. So, this is a non-issue. If we must display error messages then I would prefer using display_errors=1 instead of log_errors=1. log_errors might go everywhere... cli shows them to stderr by default iirc., I'm all for display_errors=1 too. Derick -- --- Derick Rethans http://derickrethans.nl/ JDI Media Solutions --[ if you hold a unix shell to your ear, do you hear the c? ]- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard/tests/file userstreams.phpt
This test fails with adding --INI-- output_buffering=0 output_handler= zlib.output_compression= implicit_flush=0 and even when removing the three calls to ob_xxx89 At 15:59 29.10.2002, Wez Furlong wrote: Lets stick to C comments, as those are the preference listed in coding standards (and C++ style comments are really only intended for single line out-commenting anyhow). The test works fine here; it relies on output buffering working correctly; when the test passes you see only the expected output. If it fails, you see a trace of the seek offsets and expected positioning etc. etc. The failure of the test for you, and also the strange behaviour when changing the ob_xxx calls points a finger at the output buffer layer. Lets just make it a point to discuss something before changing someone elses code: comments and coding styles are often a touchy subject with a lot of developers (I'm normally fine with it, but it seemed pointless in this case, and against our general coding standards.) --Wez. On 10/29/02, Marcus Börger [EMAIL PROTECTED] wrote: I started to work on that issue. My first attempt was to check where and why the test failed. I used the comment modification because it seems the test fails due to some internal failure. The reason i did not ask you before was that i considered my changes a kind of whitespace change so that any further change can easily be seen. The question i would like to ask now we already talk about this is: When i comment out everythink starting at ob_start() i get some output. If not (original) then i don't get any output. What is weired is that when i use any print/echo statement after ob_end_xxx() nothing is printed... The length of the lyrics added by me was only to test whether or not that part of the script works. marcus At 15:25 29.10.2002, Wez Furlong wrote: On 10/29/02, Marcus B?rger [EMAIL PROTECTED] wrote: -Use // instead of /* ... */ comments Why? #this test fails for me. Very weired... You changed the test. Why not ask me first about it failing? --Wez. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard/tests/file userstreams.phpt
On 10/29/02, Marcus Börger [EMAIL PROTECTED] wrote: This test fails with adding --INI-- output_buffering=0 output_handler= zlib.output_compression= implicit_flush=0 Works fine here. and even when removing the three calls to ob_xxx89 Can you email me the output? Also, could you strace it too? (just to be sure) --Wez. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RFC: run-tests.php errors/warnings
At 16:14 29.10.2002, Ilia A. wrote: On October 29, 2002 09:52 am, Marcus Boerger wrote: I think we need to discuss the behaviour of run-tests.php according too error/warning handling a bit. First question (let me know if i am wrong): Any error/warning/ notice in a test result is either expected or a real error. Agreed, however in 99% of the cases the data which is being outputted is what matters. As long as it is the same data as the one we expect, all the warnings/notices are irrelevant, imho. That said, ideally the tests should not cause warnings/notices, unless of course, the purpose of the test is to see if a warning/notice message will be generated. In the event a needed warning is generated, the track_errors $php_errormsg facility should be used to display the error (we already enable tracking of errors by default). Adding to block the errors is not a good approach imho, the warning should be displayed and accounted for in the expected output. Remark 1: auto_append_file= auto_prepend_file= currently do not work but that is another thread. Seems to work just fine here. Try looking at some generated messages. I allways get font...message/font which is the default. And looking into the source i saw that OnUpdateStringUnempty is used. Remark 2: We could instead use the log_errors and direct them to the output with the following changes to above settings: display_errors=0 log_errors=1 The output would be nicer but when we go to test other sapis than CGI/CLI this won't work anymore. The tests can only be performed using the cgi/cli sapis since they require a command line PHP binary. So, this is a non-issue. If we must display error messages then I would prefer using display_errors=1 instead of log_errors=1. Ilia -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] html_error related to phpinfo() output
Hi, why result the functions phpinfo() and phpcredits() as plain text when i set the html_error = Off. I think this is not the correct behavior, or not? Regards, Steve -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RFC: run-tests.php errors/warnings
At 10:14 10/29/2002 -0500, Ilia A. wrote: Adding to block the errors is not a good approach imho, the warning should be displayed and accounted for in the expected output. If your testing foo_function, it's useless when bar_function() is generating verbose warnings, so that the foo_function fails. Especially when E_ALL is set, because foo_function shouldn't generate anything. foo_function is bad bar_function is good IMO. Met vriendelijke groeten / With kind regards, Webmaster IDG.nl Melvyn Sopacua Logan I spent a minute looking at my own code by accident. Logan I was thinking What the hell is this guy doing? -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] html_error related to phpinfo() output
On Tue, 29 Oct 2002, Steve Alberty wrote: why result the functions phpinfo() and phpcredits() as plain text when i set the html_error = Off. I think this is not the correct behavior, or not? It is the correct behavior. Derick -- --- Derick Rethans http://derickrethans.nl/ JDI Media Solutions --[ if you hold a unix shell to your ear, do you hear the c? ]- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] domxml memory leak
The following fixes the memory leak of domxml002.phpt test. marcus cvs -z3 -q diff php_domxml.c (in directory S:\php4-HEAD\ext\domxml\) Index: php_domxml.c === RCS file: /repository/php4/ext/domxml/php_domxml.c,v retrieving revision 1.215 diff -u -r1.215 php_domxml.c --- php_domxml.c29 Oct 2002 16:45:19 - 1.215 +++ php_domxml.c29 Oct 2002 16:49:08 - -572,7 +572,7 zval *wrapper; int refcount = 0; /* FIXME: type check probably unnecessary here? */ - if (!node || Z_TYPE_P(node) == XML_DTD_NODE) + if (!node) /* || Z_TYPE_P(node) == XML_DTD_NODE)*/ return; wrapper = dom_object_get_data(node);
[PHP-DEV] Leak Memory Overrun in 4.3.0pre2
I'm seeing a memory overrun under PHP 4.3.0pre2 (debug) running under
Windows 2000 ISAPI. Using these two scripts:
test.php
html
head
link rel=stylesheet href=stylesheet.php type=text/css
/head
body
span class=textstyled!/span
/body
/html
stylesheet.php
--
?php
// only reload this version of the stylesheet ever hour
header(Cache-Control: max-age=3600);
?
.text {
font-size: 12px;
color: red;
font-family: Arial, Helvetica, Verdana, sans-serif
}
If in a browser window I refresh this page repeatedly within about ten
seconds I get an access violation and this debug output:
---
C:\Work\php-source\php-4.3.0pre2\ext\bcmath\libbcmath\src\init.c(72) :
Freeing 0x01B85050 (1 bytes), script=c:\inetpub\wwwroot\test.php
Last leak repeated 2 times
C:\Work\php-source\php-4.3.0pre2\ext\bcmath\libbcmath\src\init.c(57) :
Freeing 0x01B84FF8 (29 bytes), script=c:\inetpub\wwwroot\test.php
Last leak repeated 2 times
---
c:\work\php-source\php-4.3.0pre2\zend\zend_ptr_stack.c(77) : Block
0x01B80650 status:
Beginning:
Overrun (magic=0x01B80178, expected=0x7312F8DC)
End:
Unknown
---
c:\work\php-source\php-4.3.0pre2\zend\zend_hash.c(534) : ht=0x018f3484
is already destroyed
c:\work\php-source\php-4.3.0pre2\zend\zend_hash.c(660) : ht=0x018f3548
is already destroyed
---
c:\work\php-source\php-4.3.0pre2\zend\zend_ptr_stack.c(77) : Block
0x01B00650 status:
Beginning:
Overrun (magic=0x01B00178, expected=0x7312F8DC)
End:
Unknown
---
c:\work\php-source\php-4.3.0pre2\zend\zend_hash.c(534) : ht=0x01894df4
is already destroyed
c:\work\php-source\php-4.3.0pre2\zend\zend_hash.c(660) : ht=0x01894eb8
is already destroyed
---
Any tips on how to track down what's going on here?
Michael Sisolak
[EMAIL PROTECTED]
__
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard/tests/file userstreams.phpt
At 16:36 29.10.2002, Wez Furlong wrote:
On 10/29/02, Marcus Börger [EMAIL PROTECTED] wrote:
This test fails with adding
--INI--
output_buffering=0
output_handler=
zlib.output_compression=
implicit_flush=0
Works fine here.
and even when removing the three calls to ob_xxx89
Can you email me the output?
There is no output
Also, could you strace it too? (just to be sure)
[marcus@zaphod php4-HEAD]$ strace php ext/standard/tests/file/userstreams.php
execve(/usr/src/php4-HEAD/sapi/cli/php, [php,
ext/standard/tests/file/userstreams.php], [/* 39 vars */]) = 0
uname({sys=Linux, node=zaphod, ...}) = 0
brk(0) = 0x82886e4
open(/etc/ld.so.preload, O_RDONLY)= -1 ENOENT (No such file or directory)
open(/usr/local/lib/i686/mmx/libsablot.so.0, O_RDONLY) = -1 ENOENT (No
such file or directory)
stat64(/usr/local/lib/i686/mmx, 0xbfffecdc) = -1 ENOENT (No such file or
directory)
open(/usr/local/lib/i686/libsablot.so.0, O_RDONLY) = -1 ENOENT (No such
file or directory)
stat64(/usr/local/lib/i686, 0xbfffecdc) = -1 ENOENT (No such file or
directory)
open(/usr/local/lib/mmx/libsablot.so.0, O_RDONLY) = -1 ENOENT (No such
file or directory)
stat64(/usr/local/lib/mmx, 0xbfffecdc) = -1 ENOENT (No such file or
directory)
open(/usr/local/lib/libsablot.so.0, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\20H\4\000...,
1024) = 1024
fstat64(3, {st_mode=S_IFREG|0755, st_size=2611187, ...}) = 0
old_mmap(NULL, 1062104, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40016000
mprotect(0x400eb000, 189656, PROT_NONE) = 0
old_mmap(0x400eb000, 188416, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
3, 0xd4000) = 0x400eb000
old_mmap(0x40119000, 1240, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40119000
close(3)= 0
open(/usr/local/lib/libjs.so, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/X11R6/lib/i686/mmx/libjs.so, O_RDONLY) = -1 ENOENT (No such
file or directory)
stat64(/usr/X11R6/lib/i686/mmx, 0xbfffeccc) = -1 ENOENT (No such file or
directory)
open(/usr/X11R6/lib/i686/libjs.so, O_RDONLY) = -1 ENOENT (No such file or
directory)
stat64(/usr/X11R6/lib/i686, 0xbfffeccc) = -1 ENOENT (No such file or
directory)
open(/usr/X11R6/lib/mmx/libjs.so, O_RDONLY) = -1 ENOENT (No such file or
directory)
stat64(/usr/X11R6/lib/mmx, 0xbfffeccc) = -1 ENOENT (No such file or
directory)
open(/usr/X11R6/lib/libjs.so, O_RDONLY) = -1 ENOENT (No such file or
directory)
stat64(/usr/X11R6/lib, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=53720, ...}) = 0
old_mmap(NULL, 53720, PROT_READ, MAP_PRIVATE, 3, 0) = 0x4011a000
close(3)= 0
open(/usr/lib/libjs.so, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300u\1..., 1024)
= 1024
fstat64(3, {st_mode=S_IFREG|0755, st_size=445580, ...}) = 0
old_mmap(NULL, 449188, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40128000
mprotect(0x40192000, 15012, PROT_NONE) = 0
old_mmap(0x40192000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x69000) = 0x40192000
close(3)= 0
open(/usr/local/lib/libexpat.so.0, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/X11R6/lib/libexpat.so.0, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/lib/libexpat.so.0, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0@%\0\000..., 1024)
= 1024
fstat64(3, {st_mode=S_IFREG|0755, st_size=178576, ...}) = 0
old_mmap(NULL, 181656, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40196000
mprotect(0x401b9000, 38296, PROT_NONE) = 0
old_mmap(0x401b9000, 40960, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x22000) = 0x401b9000
close(3)= 0
open(/usr/local/lib/libpq.so.2, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/X11R6/lib/libpq.so.2, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/lib/libpq.so.2, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\3004\0..., 1024)
= 1024
fstat64(3, {st_mode=S_IFREG|0755, st_size=71712, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x401c3000
old_mmap(NULL, 74816, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x401c4000
mprotect(0x401d5000, 5184, PROT_NONE) = 0
old_mmap(0x401d5000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x1) = 0x401d5000
close(3)= 0
open(/usr/local/lib/libmhash.so.2, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/X11R6/lib/libmhash.so.2, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/lib/libmhash.so.2, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\360\32..., 1024)
= 1024
fstat64(3, {st_mode=S_IFREG|0755, st_size=132160, ...}) = 0
old_mmap(NULL, 135240, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x401d7000
Re: [PHP-DEV] html_error related to phpinfo() output
Shouldn't there be different settings? People may very well want html errors off, but still keep the rest of PHP 'web enabled'... At 08:58 29/10/2002, Derick Rethans wrote: On Tue, 29 Oct 2002, Steve Alberty wrote: why result the functions phpinfo() and phpcredits() as plain text when i set the html_error = Off. I think this is not the correct behavior, or not? It is the correct behavior. Derick -- --- Derick Rethans http://derickrethans.nl/ JDI Media Solutions --[ if you hold a unix shell to your ear, do you hear the c? ]- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: Unsigned Problems Revisited
On Thu, 2002-10-24 at 09:51, David M. Lloyd wrote: On Thu, 24 Oct 2002, Andi Gutmans wrote: At 02:49 PM 10/23/2002 -0500, David M. Lloyd wrote: The reality of twos-complement, bitwise arithmatic is that there are three basic shift operations: shift left, bitwise shift right, and arithmetic shift right. This simple fact is one of the basic ideas of dealing with twos-complement integers. I know that but I still wanted the opposite to be available to keep things symmetrical. I'm not sure but I think CPU's do support both logical and arithmetic shifts and just do the same with both (I might be wrong though). Generally no, it's a waste of opcode space for modern CISC processors. RISC processors often have integrated barrel-shifters, so they don't need shift instructions at all. Intel carries over arithmetic shift right instructions from older architetures for backwards-compatibility with x86, but their RISC implementation (Itanium) does not contain support for the operation. One RISC example is ARM. They give you four shift options: Logical left, logical right, arithmetic right, and rotate right. Making the operation symmetrical is a waste of precious bit combinations, and would have meant either losing another shift operation or else adding another bit to the shift operation specifier, which means that another bit would have to be sacrificed elsewhere. Another example is SPARC, which implements shifting with discrete instructions, only implents one left shift operator. PowerPC does not implement it either. Alpha has 3 instructions as well (log left, log right, arith right) Given this fact, there is no reason to have a bogus fourth operator in the name of symmetry. Mathematical operaters are simply not always symmetrical. There is no such thing as 'arithmetic shift left' or 'logical shift left' in terms of twos-complement integers, so why invent it? I agree that they don't *have* to be symmetrical but I think it's better. Better why? Anyone who understands twos-complement will understand (and expect) the ability to do those three operations, and will not be surprised by the lack of two left shifts. I argue that they *should NOT* be symmetrical because it is wrong. I have to say I agree, introducing a bogus operator could actually cause confusion. Java, which has been used several times in past arguments of why we should not do XYZ, has not had a problem with having only the operators that actually exist. Second of all, my understanding of the here-doc operator is that it acts as a unary operation. I don't see the conflict with the binary application of , given the example of unary and binary -, if it is absolutely neccessary to fulfill the (somewhat psychotic) need for symmetry where it is not realy needed, or even strictly correct. psychotic? Can we please have discussions on a professional and not personal level? It is true though, unless you can give me a sound mathematical reason that the ops should exist... and saying it looks right or it is easier is not a valid reason, becuase to those with even basic twos-complement math background, it looks wrong and is not easier. As far as I remember it does clash with here-docs. I'm pretty sure I thought of an example a while back. I can try and think of one again. In any case, I wouldn't want an overloaded operator. We try and keep away of that kind of stuff with PHP. Clashing can occur with Constant values, and functions with a \n in front of the (). Very well... then let's not put in the nonsense operator, and just have three shift operations: , , and . I agree - D [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -Jason -- Jason T. Greene [EMAIL PROTECTED] [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] html_error related to phpinfo() output
On Tue, 29 Oct 2002, Zeev Suraski wrote: Shouldn't there be different settings? People may very well want html errors off, but still keep the rest of PHP 'web enabled'... I was just stating that it was meant like this, if it should be like this is another question :) Derick -- --- Derick Rethans http://derickrethans.nl/ JDI Media Solutions --[ if you hold a unix shell to your ear, do you hear the c? ]- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Leak Memory Overrun in 4.3.0pre2
I'm seeing a memory overrun under PHP 4.3.0pre2 (debug) running under Windows 2000 ISAPI. [ . . . ] --- C:\Work\php-source\php-4.3.0pre2\ext\bcmath\libbcmath\src\init.c(72): Freeing 0x01B85050 (1 bytes), script=c:\inetpub\wwwroot\test.php Last leak repeated 2 times C:\Work\php-source\php-4.3.0pre2\ext\bcmath\libbcmath\src\init.c(57): Freeing 0x01B84FF8 (29 bytes), script=c:\inetpub\wwwroot\test.php Last leak repeated 2 times Based on seeing these leaks I disabled BCMath and recompiled PHP. Without BCMath active I do not have any of the memory overruns that I reported in my previous message. Looking in the CVS logs for php4/ext/bcmath/bcmath.c I believe there may be an issue with the changes introduced in version 1.37 (by Andi, who is CCed also). This patch moved the allocation and freeing of the static BC numbers _zero_, _one_, and _two_ to a per-request basis instead of at module initilzation and shutdown. It looks like the storage locations for those values are global externs, however, which multiple threads are now allocating and deallocating at the same time. Is there somewhere that I'm not understanding in the code that would keep multiple threads from smashing each other here? Michael Sisolak [EMAIL PROTECTED] __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] html_error related to phpinfo() output
On Tue, 29 Oct 2002, Zeev Suraski wrote: Shouldn't there be different settings? People may very well want html errors off, but still keep the rest of PHP 'web enabled'... I've asked about this a few times..I guess it was easier to use existing global than add new? :) This doesn't need to be any ini-setting, IMO. Only CLI needs this. --Jani -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard/tests/file userstreams.phpt
OK, so how about a backtrace ? --Wez. On Tue, 29 Oct 2002, Marcus [iso-8859-1] Börger wrote: At 16:36 29.10.2002, Wez Furlong wrote: Also, could you strace it too? (just to be sure) old_mmap(NULL, 266240, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x407d5000 read(3, ...naq gur ebnq orpbzrf zl oevqr..., 8192) = 8192 lseek(3, 0, SEEK_SET) = 0 --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] html_error related to phpinfo() output
On Tue, 29 Oct 2002, Jani Taskinen wrote: On Tue, 29 Oct 2002, Zeev Suraski wrote: Shouldn't there be different settings? People may very well want html errors off, but still keep the rest of PHP 'web enabled'... I've asked about this a few times..I guess it was easier to use existing global than add new? :) This doesn't need to be any ini-setting, IMO. Only CLI needs this. +1 on that. Derick -- --- Derick Rethans http://derickrethans.nl/ JDI Media Solutions --[ if you hold a unix shell to your ear, do you hear the c? ]- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RFC: run-tests.php errors/warnings
The tests can only be performed using the cgi/cli sapis since they require a command line PHP binary. So, this is a non-issue. If we must display error messages then I would prefer using display_errors=1 instead of log_errors=1. Ilia I'm working with another person on a web version of the test script, and on a multithreaded test script. Purpose is to test multithread support, and hopefully start finding the issues, under IIS and Apache 2. Shane -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: Leak Memory Overrun in 4.3.0pre2
You are right. I screwed up. I have to make these TSRM globals. I'll try and do it tomorrow. Andi At 09:44 AM 10/29/2002 -0800, Michael Sisolak wrote: I'm seeing a memory overrun under PHP 4.3.0pre2 (debug) running under Windows 2000 ISAPI. [ . . . ] --- C:\Work\php-source\php-4.3.0pre2\ext\bcmath\libbcmath\src\init.c(72): Freeing 0x01B85050 (1 bytes), script=c:\inetpub\wwwroot\test.php Last leak repeated 2 times C:\Work\php-source\php-4.3.0pre2\ext\bcmath\libbcmath\src\init.c(57): Freeing 0x01B84FF8 (29 bytes), script=c:\inetpub\wwwroot\test.php Last leak repeated 2 times Based on seeing these leaks I disabled BCMath and recompiled PHP. Without BCMath active I do not have any of the memory overruns that I reported in my previous message. Looking in the CVS logs for php4/ext/bcmath/bcmath.c I believe there may be an issue with the changes introduced in version 1.37 (by Andi, who is CCed also). This patch moved the allocation and freeing of the static BC numbers _zero_, _one_, and _two_ to a per-request basis instead of at module initilzation and shutdown. It looks like the storage locations for those values are global externs, however, which multiple threads are now allocating and deallocating at the same time. Is there somewhere that I'm not understanding in the code that would keep multiple threads from smashing each other here? Michael Sisolak [EMAIL PROTECTED] __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Italian Book on PHP 5
Hi, I'm writing a php's book for italian people. I need to know some info about php 5.0. Any ideal time line ?? Tnx in advance. Ah, how can I get the HEAD cvs ? tnx -- -- Vecchioni da ragazzo si chiamava Jovanotti ? -- Michel ZioBudda Morelli [EMAIL PROTECTED] ICQ UIN: 58351764 PR of Linux in Italy http://www.ziobudda.net http://www.phpdev.it -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard/tests/file userstreams.phpt
(gdb) file /usr/src/php4-HEAD/sapi/cli/php Reading symbols from /usr/src/php4-HEAD/sapi/cli/php...done. (gdb) set args ext/standard/tests/file/userstreams.phpt (gdb) run Starting program: /usr/src/php4-HEAD/sapi/cli/php ext/standard/tests/file/userstreams.phpt [New Thread 1024 (LWP 13760)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 13760)] 0x081cb069 in zend_assign_add_obj_handler (execute_data=0xbfffa520, op_array=0x407581bc, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:232 232 if ((*object_ptr)-type == IS_NULL (gdb) bt #0 0x081cb069 in zend_assign_add_obj_handler (execute_data=0xbfffa520, op_array=0x407581bc, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:232 #1 0x081c34de in execute (op_array=0x407581bc, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:1194 #2 0x081a9f7c in call_user_function_ex (function_table=0x4073e74c, object_pp=0x40798984, function_name=0xbfffa6a0, retval_ptr_ptr=0xbfffa694, param_count=1, params=0xbfffa698, no_separation=0, symbol_table=0x0, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute_API.c:646 #3 0x081944f7 in php_userstreamop_read (stream=0x40799760, buf=0x407cea4c , count=8192, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/main/user_streams.c:444 #4 0x0818cdb9 in php_stream_fill_read_buffer (stream=0x40799760, size=1023, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/main/streams.c:491 #5 0x0818d1e0 in _php_stream_get_line (stream=0x40799760, buf=0x407ce610 , maxlen=1024, returned_len=0xbfffa770, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/main/streams.c:758 #6 0x08120a1c in zif_fgets (ht=2, return_value=0x407cc368, this_ptr=0x0, return_value_used=1, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/ext/standard/file.c:1341 #7 0x081d4bfa in zend_do_fcall_common_helper (execute_data=0xbfffd7b0, op_array=0x40738864, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:2414 ---Type return to continue, or q return to quit--- #8 0x081d5419 in zend_do_fcall_handler (execute_data=0xbfffd7b0, op_array=0x40738864, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:2533 #9 0x081c34de in execute (op_array=0x40738864, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:1194 #10 0x081b3177 in zend_execute_scripts (type=8, tsrm_ls=0x82887b0, retval=0x0, file_count=3) at /usr/src/php4-HEAD/Zend/zend.c:862 #11 0x08183f99 in php_execute_script (primary_file=0xbab0, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/main/main.c:1541 #12 0x081dfa30 in main (argc=2, argv=0xbb44) at /usr/src/php4-HEAD/sapi/cli/php_cli.c:695 #13 0x40561280 in __libc_start_main () from /lib/libc.so.6 (gdb) At 19:02 29.10.2002, you wrote: OK, so how about a backtrace ? --Wez. On Tue, 29 Oct 2002, Marcus [iso-8859-1] Börger wrote: At 16:36 29.10.2002, Wez Furlong wrote: Also, could you strace it too? (just to be sure) old_mmap(NULL, 266240, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x407d5000 read(3, ...naq gur ebnq orpbzrf zl oevqr..., 8192) = 8192 lseek(3, 0, SEEK_SET) = 0 --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Italian Book on PHP 5
Hi, I'm writing a php's book for italian people. I need to know some info about php 5.0. Any ideal time line ?? Tnx in advance. This could be a help: http://www.zend.com/engine2/ZendEngine-2.0.pdf Ah, how can I get the HEAD cvs ? Probably at http://cvs.php.net/ Jome -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] [CVS Questions] ext/sybase_ct
Hi, from http://www.zend.com/zend/week/week109.php: --- TLK: sybase_ct maintainer Timm Friebe has volunteered to take over maintenance of the sybase_ct extension. He has made a number of patches to the code (which can be seen here) and has been running then under a high-load production environment for over a month. At this stage these fixes may still be included in the next release candidate for 4.3.0. --- I'd love to see this happen, but - since I'm new to PHP development - I would like to make sure what I'm doing (or going to do) is right. README.CVS-RULES 1. Respect other people working on the project. Last commit: 2002/03/12 - I guess there aren't too many people actively working on ext/sybase_ct:) README.CVS-RULES 2. Discuss any significant changes on the list before committing. friebes:~/devel/php4/ext/sybase_ct cvs diff php_sybase_ct.c |wc -l 1254 friebes:~/devel/php4/ext/sybase_ct cvs diff php_sybase_ct.h |wc -l 79 I guess this is significant. [...] README.CVS-RULES 5. If you don't know how to do something, ask first! OK, that's simple. * Do I commit this against head or against php_4_3_0pre2? (cvs com cvs tag -F php_4_3_0pre2 or simply cvs com)? * buildconf says: You need bison version = 1.30 = 1.75 installed to build PHP from CVS - I'm running FreeBSD 4.7-STABLE, bison from ports is 1.35_1 *and* You need libtool version 1.4 or newer installed - libtool from ports is 1.3.4_4 Are there other people here with FreeBSD and what do you do? Compile your own libtool/bison? So far, I've stuck to snaps which worked fine for me... * Who writes documentation? http://bugs.php.net/bug.php?id=16960 contains working examples of the enhancement, more would come. Do I need special docs karma for this? README.CVS-RULES 6. Test your changes before committing them. We mean it. Really. As promised, I compiled it into php-4.2.2 under FreeBSD and under Debian on a production environment - it's served nearly 100 million HTTP requests there by today and completed a couple of hundred thousand SQL queries. *What* was tested is the old functionality, without relying on new features, so that a switchback would be easily manageable in an urgent situation. Though, since the majority of the new functionality is handled via lines of source that are also called with the old api, it should be OK. README.CVS-RULES [...About CVS log...] This is what I would write: # Add myself to authors - Take care of feature/changes requests by myself in (Bug #16960): * Implement unbuffered queries * Fix up sybase_fetch_object not to return objects with numeric members * Fix issues with identical fieldnames * Set data types returned to their equivalents in PHP if possible * Add server message handler * Add a new ini setting for deadlock retries, defaulting to forever. Deadlocks within transaction can cause transtate to output uncorrect values if they are retried. * Add a new function sybase_fetch_assoc - Make sybase_query errors more verbose - Make phpinfo() output more verbose - Add mssql-aliases to all the new functionality Is this too short? Or to long? BUGS There are four open bugs for ext/sybase_db. I don't use this extension and its usage is discouraged anyway (see http://www.isug.com/Sybase_FAQ/ASE/section7.html#7.2). There is one open bug for ext/sybase_ct concerning compute results and multiple results, pointing to: * http://bugs.php.net/bug.php?id=11475 This breaks functionality on further queries, producing weird results. If you can't handle multiple resultsets, you *must* cancel them! * http://bugs.php.net/bug.php?id=13735 Bogus * http://bugs.php.net/bug.php?id=12074 Feature request for unbuffered_query:) * http://bugs.php.net/bug.php?id=13475 http://www.marden.org/php-sybase-ct/ gives me a 404 I'll have a look at it nevertheless TESTS = As I can only test my development on FreeBSD (4.3, 4.7) and FreeTDS (0.60) w/ Sybase (11.0.3.3/Unix, 12.5/Linux, 12.5.0.1/Sun) and Debian w/ native Sybase-libraries Sybase (12.5/Linux, 12.5.0.1/Sun), I'd be happy about any feedback on other systems and constellations. Whew, I hope I'm not forgetting anything? -- Timm Any sufficiently advanced bug is indistinguishable from a feature -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] functions in time.c
Shouldn't microtime and gettimeofday be unavailable
when HAVE_GETTIMEOFDAY is undefined?
PHP_FUNCTION(microtime)
{
#ifdef HAVE_GETTIMEOFDAY
...
#endif
RETURN_FALSE;
}
PHP_FUNCTION(gettimeofday)
{
#ifdef HAVE_GETTIMEOFDAY
...
#endif
RETURN_FALSE;
}
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] [CVS Questions] ext/sybase_ct
On 29 Oct 2002, Timm Friebe wrote: * Do I commit this against head or against php_4_3_0pre2? (cvs com cvs tag -F php_4_3_0pre2 or simply cvs com)? HEAD. * buildconf says: You need bison version = 1.30 = 1.75 installed to build PHP from CVS - I'm running FreeBSD 4.7-STABLE, bison from ports is 1.35_1 *and* You need libtool version 1.4 or newer Those are the requirements. Not our problem to solve those for you, do as you feel best. Compiling from sources sounds like a good idea. (for bison, use 1.28 version) README.CVS-RULES 6. Test your changes before committing them. We mean it. Really. As promised, I compiled it into php-4.2.2 under FreeBSD and under Debian That means that you test that your changes to CVS HEAD work before you commit them to CVS _HEAD_ not some old release. README.CVS-RULES [...About CVS log...] This is what I would write: I should rewrite that thing.. # Add myself to authors # is not needed here. - Take care of feature/changes requests by myself in (Bug #16960): * Implement unbuffered queries * Fix up sybase_fetch_object not to return objects with numeric members * Fix issues with identical fieldnames * Set data types returned to their equivalents in PHP if possible * Add server message handler * Add a new ini setting for deadlock retries, defaulting to forever. Deadlocks within transaction can cause transtate to output uncorrect values if they are retried. * Add a new function sybase_fetch_assoc Please READ the NEWS file in HEAD and compare it to this. Does any entry in it look like this? Added, Fixed, Removed, Made. (past tense!) (Take care? Huh?) - Make sybase_query errors more verbose - Make phpinfo() output more verbose - Add mssql-aliases to all the new functionality Is this too short? Or to long? Both. Read the NEWS file entries for 4.3.0 carefully. Every entry needs to have your name behind it: - Made sybase_query() error messages more verbose. (Timm) Notice the ()'s? And be verbose but not too verbose in these NEWS entries too. There are four open bugs for ext/sybase_db. I don't use this extension and its usage is discouraged anyway (see http://www.isug.com/Sybase_FAQ/ASE/section7.html#7.2). Move it to PECL then. There is one open bug for ext/sybase_ct concerning compute results and multiple results, pointing to: * http://bugs.php.net/bug.php?id=11475 This breaks functionality on further queries, producing weird results. If you can't handle multiple resultsets, you *must* cancel them! * http://bugs.php.net/bug.php?id=13735 Bogus * http://bugs.php.net/bug.php?id=12074 Feature request for unbuffered_query:) * http://bugs.php.net/bug.php?id=13475 http://www.marden.org/php-sybase-ct/ gives me a 404 I'll have a look at it nevertheless Bogus - Mark it as such and be done with it. Feature request - change the category to Feature/Change Request Try always first to get them to test the latest snapshot. (Use the quick-resolve select box, or the urls in the mails on php-bugs list) As I can only test my development on FreeBSD (4.3, 4.7) and FreeTDS (0.60) w/ Sybase (11.0.3.3/Unix, 12.5/Linux, 12.5.0.1/Sun) and Debian w/ native Sybase-libraries Sybase (12.5/Linux, 12.5.0.1/Sun), I'd be happy about any feedback on other systems and constellations. We use users for testing. See above comment about snapshots.. --Jani -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] functions in time.c
Of course.
--Jani
On Tue, 29 Oct 2002, Marcus Boerger wrote:
Shouldn't microtime and gettimeofday be unavailable
when HAVE_GETTIMEOFDAY is undefined?
PHP_FUNCTION(microtime)
{
#ifdef HAVE_GETTIMEOFDAY
...
#endif
RETURN_FALSE;
}
PHP_FUNCTION(gettimeofday)
{
#ifdef HAVE_GETTIMEOFDAY
...
#endif
RETURN_FALSE;
}
--
- For Sale! -
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] CVS Account Request: jaenecke
I am mainly interested in working on the manual; completing the german version (I am german, never mind the email .li), clearing unclear passages etc. But I also could imagine to do a little debugging -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard/tests/file userstreams.phpt
Is that ZE2? There is no zend_assign_add_obj_handler function anywhere in my checkout of HEAD + ZE1, and line 232 of zend_execute is a case statement in my checkout. I'm not concerned with ZE2 problems at this time (well, I am, but don't have the time to support it). Most likely, this is an issue with the recent splitting of the opcode handlers; Andi would probably like to see this backtrace. --Wez. On 29/10/02, Marcus Börger [EMAIL PROTECTED] wrote: (gdb) file /usr/src/php4-HEAD/sapi/cli/php Reading symbols from /usr/src/php4-HEAD/sapi/cli/php...done. (gdb) set args ext/standard/tests/file/userstreams.phpt (gdb) run Starting program: /usr/src/php4-HEAD/sapi/cli/php ext/standard/tests/file/userstreams.phpt [New Thread 1024 (LWP 13760)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 13760)] 0x081cb069 in zend_assign_add_obj_handler (execute_data=0xbfffa520, op_array=0x407581bc, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:232 232 if ((*object_ptr)-type == IS_NULL (gdb) bt #0 0x081cb069 in zend_assign_add_obj_handler (execute_data=0xbfffa520, op_array=0x407581bc, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:232 #1 0x081c34de in execute (op_array=0x407581bc, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:1194 #2 0x081a9f7c in call_user_function_ex (function_table=0x4073e74c, object_pp=0x40798984, function_name=0xbfffa6a0, retval_ptr_ptr=0xbfffa694, param_count=1, params=0xbfffa698, no_separation=0, symbol_table=0x0, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute_API.c:646 #3 0x081944f7 in php_userstreamop_read (stream=0x40799760, buf=0x407cea4c , count=8192, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/main/user_streams.c:444 #4 0x0818cdb9 in php_stream_fill_read_buffer (stream=0x40799760, size=1023, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/main/streams.c:491 #5 0x0818d1e0 in _php_stream_get_line (stream=0x40799760, buf=0x407ce610 , maxlen=1024, returned_len=0xbfffa770, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/main/streams.c:758 #6 0x08120a1c in zif_fgets (ht=2, return_value=0x407cc368, this_ptr=0x0, return_value_used=1, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/ext/standard/file.c:1341 #7 0x081d4bfa in zend_do_fcall_common_helper (execute_data=0xbfffd7b0, op_array=0x40738864, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:2414 ---Type return to continue, or q return to quit--- #8 0x081d5419 in zend_do_fcall_handler (execute_data=0xbfffd7b0, op_array=0x40738864, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:2533 #9 0x081c34de in execute (op_array=0x40738864, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/Zend/zend_execute.c:1194 #10 0x081b3177 in zend_execute_scripts (type=8, tsrm_ls=0x82887b0, retval=0x0, file_count=3) at /usr/src/php4-HEAD/Zend/zend.c:862 #11 0x08183f99 in php_execute_script (primary_file=0xbab0, tsrm_ls=0x82887b0) at /usr/src/php4-HEAD/main/main.c:1541 #12 0x081dfa30 in main (argc=2, argv=0xbb44) at /usr/src/php4-HEAD/sapi/cli/php_cli.c:695 #13 0x40561280 in __libc_start_main () from /lib/libc.so.6 (gdb) At 19:02 29.10.2002, you wrote: OK, so how about a backtrace ? --Wez. On Tue, 29 Oct 2002, Marcus [iso-8859-1] Börger wrote: At 16:36 29.10.2002, Wez Furlong wrote: Also, could you strace it too? (just to be sure) old_mmap(NULL, 266240, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x407d5000 read(3, ...naq gur ebnq orpbzrf zl oevqr..., 8192) = 8192 lseek(3, 0, SEEK_SET) = 0 --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] CVS Account Request: adamchan
Translating the documentation -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installation instructions
At 11:30 10/29/2002 +0100, Friedhelm Betz wrote:
I think, it would be nice to add information to one place, the
documentation
about Apache 2 support.
1. It's not production ready
Ah yes - but that will contradict greatly, to the best version yet
marketing
trick the Apache Group is advertising on their front page.
We can mention it to users, in the bug db etc. But officially
documenting, that
Apache 2 is really a beta product, doesn't really express consistency,
between
the family.
I thought it more from another point of view: the support for apache2
in php is not production stable ,e.g. the sapi in php :-)
That's exactly what is the perception. I can live with that, but it's not very
stimulating for the people that work on apachefilter.
Since the 'official' release, Apache has changed it's API breaking BC 2 times
already. How can extension developers work on improvement then?
Maybe this is due to the fact (?) that apache2 is still beta (I really
don't know) but form the php-side point of view, php-versions are not
production stable in conjunction with apache2.
Maybe for windows it's the better version - I have no idea.
For unix it's far from that.
As Derick said, I don't
think this will hurt someone of the apachegroup.
Fine with me - we all know better -;)
/MELVYN
void wakeup() {
for(unsigned int cuppajava;drink();cuppajava++);
}
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installation instructions
1. It's not production ready Ah yes - but that will contradict greatly, to the best version yet marketing trick the Apache Group is advertising on their front page. We can mention it to users, in the bug db etc. But officially documenting, that Apache 2 is really a beta product, doesn't really express consistency, between the family. I'm aware that this is not a technical reason not to do this, I'm just pointing out how this can be perceived. As far as I can see, we should not not put into the PHP documentation that Apache 2 is not production ready, but PHP is not production ready for Apache 2. This is of course shows us in a negative manner, but we need to make our users be aware of the fact that PHP should not be used for production in Apache 2 (as long as this is the case). Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installationinstructions
On Tue, 29 Oct 2002, Gabor Hojtsy wrote: As far as I can see, we should not not put into the PHP documentation that Apache 2 is not production ready, but PHP is not production ready for Apache 2. But it's incorrect :). By saying Do not use Apache 2 and PHP in a production environment you don't blame any of the two projects. Derick -- --- Derick Rethans http://derickrethans.nl/ JDI Media Solutions --[ if you hold a unix shell to your ear, do you hear the c? ]- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installation instructions
Derick Rethans writes: On Tue, 29 Oct 2002, Gabor Hojtsy wrote: As far as I can see, we should not not put into the PHP documentation that Apache 2 is not production ready, but PHP is not production ready for Apache 2. But it's incorrect :). By saying Do not use Apache 2 and PHP in a production environment you don't blame any of the two projects. I agree with Derick's approach. There's no need to cast dispersions on either Apache2 or PHP. Simply stating _clearly_ that the combination of PHP4 and Apache2 should not be used in a production environment is sufficient. No need to play the blame-game. :) Regards Mike Robinson -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] RE: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC]Apache 2 installation instructions
As far as I can see, we should not not put into the PHP documentation that Apache 2 is not production ready, but PHP is not production ready for Apache 2. But it's incorrect :). By saying Do not use Apache 2 and PHP in a production environment you don't blame any of the two projects. I agree with Derick's approach. There's no need to cast dispersions on either Apache2 or PHP. Simply stating _clearly_ that the combination of PHP4 and Apache2 should not be used in a production environment is sufficient. No need to play the blame-game. :) Ack. So then, please add us some info on PHP - Apache2 versions compatibility so we can add the info to the docs. Or is it only Sascha who knows this (apache2 sapi author)? Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installation instructions
I think, it would be nice to add information to one place, the documentation about Apache 2 support. 1. It's not production ready Ah yes - but that will contradict greatly, to the best version yet marketing trick the Apache Group is advertising on their front page. We can mention it to users, in the bug db etc. But officially documenting, that Apache 2 is really a beta product, doesn't really express consistency, between the family. I thought it more from another point of view: the support for apache2 in php is not production stable ,e.g. the sapi in php :-) That's exactly what is the perception. I can live with that, but it's not very stimulating for the people that work on apachefilter. Since the 'official' release, Apache has changed it's API breaking BC 2 times already. How can extension developers work on improvement then? For sure I don't want to blame anybody working on the php sapi for apache2 nor discourage them :-) I believe they do their best... Maybe this is due to the fact (?) that apache2 is still beta (I really don't know) but form the php-side point of view, php-versions are not production stable in conjunction with apache2. Maybe for windows it's the better version - I have no idea. For unix it's far from that. As Derick said, I don't think this will hurt someone of the apachegroup. Fine with me - we all know better -;) ;-) Friedhelm -- +++ GMX - Mail, Messaging more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen! -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-DOC] Apache 2 installation instructions
I did more work and testing with fastcgi and apache 2, and have php 4.3 running under apache 2. Since it's out of process, no multithread issues which are one of the major issues. I didn't write docs, but there are some in sapi/cgi/README.fastcgi Shane As far as I can see, we should not not put into the PHP documentation that Apache 2 is not production ready, but PHP is not production ready for Apache 2. This is of course shows us in a negative manner, but we need to make our users be aware of the fact that PHP should not be used for production in Apache 2 (as long as this is the case). Goba -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Work is beginning on cURL and PHP again
Hi, this may be a bit late: On Mon, Oct 21, 2002 at 10:12:55PM +0200, Sterling Hughes wrote : * allowing persistent cURL handles that survive the request, for HTTP 1.1 persistent connections Why only for persistent HTTP/1.1 connection and not other type of curl resources like FTP connections? -- GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc $ grep docref_root php.ini docref_root = http://landonize.it/?how=urltheme=classicfilter=RichyHuser=imajesurl=http%3A%2F%2Fphp.net%2F/; -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] CVS Account Request: potatotsang
To join developing PHP. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Karma for php4 and bcompiler
Hi there, with not so much time to dedicate to php improvements and bug fixes I want to have karma to help fix some bugs/improvements into php and into bcompiler for win32 that is my speciallity. I've already did a compile with windows but now I need to add some more functionalities. Alan Knowles already said to me to keep in touch. Thanks, Ernani -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Karma for php4 and bcompiler
Ernani helped out with bcompiler - so karma on that is ok. I think for php4 you will have to send patches to php-dev for the time being. until they get used to you :) Regards Alan Ernani Joppert Pontes Martins wrote: Hi there, with not so much time to dedicate to php improvements and bug fixes I want to have karma to help fix some bugs/improvements into php and into bcompiler for win32 that is my speciallity. I've already did a compile with windows but now I need to add some more functionalities. Alan Knowles already said to me to keep in touch. Thanks, Ernani -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Karma for php4 and bcompiler
I'll add the pear karma once I figure out which of his 2 cvs accounts he uses. On Wed, 30 Oct 2002, Alan Knowles wrote: Ernani helped out with bcompiler - so karma on that is ok. I think for php4 you will have to send patches to php-dev for the time being. until they get used to you :) Regards Alan Ernani Joppert Pontes Martins wrote: Hi there, with not so much time to dedicate to php improvements and bug fixes I want to have karma to help fix some bugs/improvements into php and into bcompiler for win32 that is my speciallity. I've already did a compile with windows but now I need to add some more functionalities. Alan Knowles already said to me to keep in touch. Thanks, Ernani -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] functions in time.c
On Tue, 29 Oct 2002, Marcus Boerger wrote: Shouldn't microtime and gettimeofday be unavailable when HAVE_GETTIMEOFDAY is undefined? IMO they should indeed not be available in that case. Derick -- --- Derick Rethans http://derickrethans.nl/ JDI Media Solutions --[ if you hold a unix shell to your ear, do you hear the c? ]- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
