Re: mac os x, test failure
| From: | Alexey Zakhlestin | Date: | Wed, 02 Jul 2008 06:19:13 +0000 |
| Subject: | Re: mac os x, test failure | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-38697@lists.php.net to get a copy of this message | ||
some more details.
the return-chain in this case is following:
virtual_file_ex(..., path, ...) -> returns 1, because path_length >= MAXPATHLEN
expand_filepath(filepath, ...) -> returns null
_php_stream_fopen(filename, ...) -> returns null
php_plain_files_stream_opener(..., path, ...) -> returns null
_php_stream_open_wrapper_ex(path, ...) calls php_stream_display_wrapper_errors()
php_stream_display_wrapper_errors() checks errno-value
I don't see how any function here might set errno to any value. How
does this work on other operating-systems?
On Mon, Jun 30, 2008 at 12:29 PM, Alexey Zakhlestin <indeyets@gmail.com> wrote:
> On Mon, Jun 30, 2008 at 12:27 PM, Antony Dovgal <tony@daylessday.org> wrote:
>> On 30.06.2008 12:24, Alexey Zakhlestin wrote:
>>>>
>>>> It might also mean that the error message is different on Mac OS or the
>>>> error code is different.
>>>> I've seen that many times on different platforms.
>>>
>>> that's what I thought at first, but testing showed, that it is not that
>>> simple.
>>>
>>> plain fopen() in C on large file-name results in "File name too long"
>>> error.
>>> php never reaches open() call and error "Inappropriate ioctl for
>>> divice" is already set at the very first line of php_execute_script
>>> (probably even earlier)
>>> looks like there's some uncaught error during initialization of php
>>
>> Do you have a strace log?
>
> I will try to make one (we use dtrace here)
>
>
>
> --
> Alexey Zakhlestin
> http://blog.milkfarmsoft.com/
>
--
Alexey Zakhlestin
http://blog.milkfarmsoft.com/