Red Hat Bugzilla – Bug 121011
PHP 4.3.6 update for Fedora Core 2
Last modified: 2007-11-30 17:10:40 EST
Description of problem:
[15-Apr-2004] The PHP Development Team is proud to announce the
release of PHP 4.3.6. This is is a bug fix release whose primary
goal is to address two bugs which may result in crashes in PHP
builds with thread-safety enabled. All in all this release fixes
approximately 25 bugs that have been discovered since the 4.3.5
Version-Release number of selected component (if applicable):
Patch1: Can be removed, fixed in php-4.3.5rc1
Patch2: Has to re-enable (attached php-4.3.6-config.patch)
Patch8: Has to re-enable (attached php-4.3.6-miscfix.patch)
Patch9: Can be removed, fixed in php-4.3.5rc1
Patch10: Can be removed, fixed in php-4.3.5rc1
Patch23: Can be removed, fixed in php-4.3.5rc2
Patch30: Has to re-enable (attached php-4.3.5-dlopen.patch)
Please update to PHP 4.3.6 :-)
Created attachment 99462 [details]
Re-enabled config patch for 4.3.6
Created attachment 99463 [details]
Re-enabled miscfix patch for 4.3.6
Created attachment 99464 [details]
Re-enabled dlopen patch for >= 4.3.5
Great stuff, thanks Robert. Building into Raw Hide now. I'll do an
FC1 update for this one too.
Actually, this won't show up in Raw Hide for a while, there is a
showstopper in 4.3. which is now being triggered (upstream #27810).
I'm build the fix but it needs more testing.
I noticed, that the restart executed by logrotate on some systems
kills the httpd, if php 4.3. is used. I still don't know how to
reproduce that breakdown and I don't know what that problem causes.
Even your patch for upstream #27810 doesn't solve it.
Maybe you are able to reproduce and track down this...
So I think, it's really okay that only 4.3.4 is used for FC2 (as it
A problem separate from the mod_python issue, I take it? If the
parent is segfaulting can you get a core dump?
echo "CoreDumpDirectory /tmp" > /etc/httpd/conf.d/core.conf
is sufficient to get a core dump in /tmp with the FC2 httpd package.
I think it is a separate issue from mod_python, and I attached the
backtrace from the core dump of the logrotate restart - maybe it
--- snipp ---
#0 0x406e5840 in ?? ()
#1 0x08064711 in regex_cleanup ()
#2 0x4016125d in run_cleanups (cref=0x808dd40) at apr_pools.c:1979
#3 0x40160909 in apr_pool_clear (pool=0x808dd30) at apr_pools.c:718
#4 0x08062c52 in main ()
#5 0x42015704 in __libc_start_main () from /lib/tls/libc.so.6
--- snapp ---
Sorry, backtrace is only such short - apr, apr-utils and httpd are
the latest ones.
This is exactly the backtrace you get without the fix I posted on
apache.org/~jorton for upstream #27810. Are you sure you had the
Waahh...pleae forget it, I used the wrong (unpatched) binary :-(
Thank you very very much for your help :)
Re-opened for tracking as update to FC2.
php-4.3.6-5 has been issued to the FC2 "testing" repos; please report
results of testing here.
php-4.3.6-5 works very well here at my computers :)
Thanks for your feedback.