ID:               48744
 Comment by:       dougcsd at yahoo dot com
 Reported By:      tom at ideaweb dot de
 Status:           Feedback
 Bug Type:         Safe Mode/open_basedir
 Operating System: Linux Debian Etch
 PHP Version:      5.3.0
 Assigned To:      fb-req-jani
 New Comment:

Here is more info on this.  

I ran into this earlier while running 5.3 Alpha snapshots.

The Snapshot:  php5.3-200810090430 (Alpha 3) did not seem to have this
problem yet, and works ok.  I have reproduced the problem on two
machines and multiple operating systems.  I see the scrambled open
basedir paths in the apache logs when a simple phpinfo() fails.

Both systems were running Slackware 12.1 (one 32 bit, and one 64 bit)
BlueWhite64 for the 12.1 64 bit.

I recently upgraded to Slackware 12.2 on the 32 bit machine to upgrade
the libc to a newer version and see if it helped, but the problem
persists.

I first saw this problem in php5.3-200903230730, and assumed it was a
development bug that would work itself out in time, and simply reverted
back.  However the problem has carried over to 5.3.0 release.

I have done a bit of digging and it appears that both PHP and Apache
are using pthreads on these machines.  Because of the randomness of when
the corruption occurs, I believe this may be related to a threading
issue, but I have yet to discover any additional details.


Previous Comments:
------------------------------------------------------------------------

[2009-07-16 13:08:25] j...@php.net

Have you figured out the differences between the working and
non-working servers running 5.3 yet? That's propably the only way to
debug this. Otherwise, just let this rot. 

------------------------------------------------------------------------

[2009-07-15 07:29:24] tom at ideaweb dot de

Sorry for the delay, the test server was in use...

Seems to be the same =(

(gdb) run -X -d /www/apache/current/
Starting program: /www/apache/2.2.11/bin/httpd -X -d 
/www/apache/current/
Failed to read a valid object file image from memory.
[Thread debugging using libthread_db enabled]
[New Thread -1212967232 (LWP 27684)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1212967232 (LWP 27684)]
0xb755848f in OnUpdateBaseDir (entry=0x824fbb8, 
    new_value=0x83b5070 
"/www/htdocs/ecolint.ch/dev:/www/htdocs/ecolint.ch/tmp:/www/htdocs/eco
lint.ch/mysql", 
    new_value_length=82, mh_arg1=0x48, mh_arg2=0xb7b37e80, 
mh_arg3=0x0, stage=4)
    at /www/src/php5.3-200907101630/main/fopen_wrappers.c:103
103             if (!*p || !**p) {
(gdb)

------------------------------------------------------------------------

[2009-07-10 22:15:18] j...@php.net

Is the backtrace the same?

------------------------------------------------------------------------

[2009-07-10 18:46:07] tom at ideaweb dot de

Keeps crashing with php5.3-200907101630 =(

[Fri Jul 10 20:41:45 2009] [notice] child pid 13862 exit signal 
Segmentation fault (11)
[Fri Jul 10 20:41:47 2009] [notice] child pid 13863 exit signal 
Segmentation fault (11)

------------------------------------------------------------------------

[2009-07-10 18:26:39] j...@php.net

Please try using this CVS snapshot:

  http://snaps.php.net/php5.3-latest.tar.gz
 
For Windows:

  http://windows.php.net/snapshots/

Just in case this is just another side-effect caused by another bug..

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/48744

-- 
Edit this bug report at http://bugs.php.net/?id=48744&edit=1

Reply via email to