#45044 [Fbk->Csd]: relative paths not resolved correctly

[email protected]
Newsgroups php.bugs
Message-ID <[email protected]>
 ID:               45044
 Updated by:       [email protected]
 Reported By:      felipensp at gmail dot com
-Status:           Feedback
+Status:           Closed
 Bug Type:         Scripting Engine problem
 Operating System: FreeBSD 6.3
 PHP Version:      5.3CVS-2008-05-20 (CVS)
-Assigned To:      fb-req-jani
+Assigned To:      dmitry
 New Comment:

Fixed in CVS HEAD and PHP_5_3.


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

[2008-08-12 08:55:49] [email protected]

Isn't this fixed now by Dmitry's commit..?

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

[2008-08-06 15:33:54] [email protected]

Dmitry, could you take a look at this, plz?

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

[2008-08-06 15:33:28] [email protected]

I can verify this on OS X 10.4 with this reproducable script

http://trash.chregu.tv/include-bug.php.txt




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

[2008-07-24 19:27:21] [email protected]

virtual_file_ex() assume that if realpath() does not return NULL the
file exists. 

The problem is that FreeBSD's realpath() will not return NULL if all
components *but the last* exist.

So php_resolve_path()/tsrm_realpath() will pass
/usr/home/felipe/foo.php to virtual_file_ex() and assume it exists.

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

[2008-05-30 20:19:00] [email protected]

status->verified 

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

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/45044

-- 
Edit this bug report at http://bugs.php.net/?id=45044&edit=1
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.