Re: PEAR !<3 xdebug
| From: | Matthew Fonda | Date: | Mon, 07 Feb 2011 15:47:59 +0000 |
| Subject: | Re: PEAR !<3 xdebug | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-54071@lists.php.net to get a copy of this message | ||
On Sun, Feb 6, 2011 at 8:05 PM, David Muir <davidkmuir@gmail.com> wrote:
> Hi all,
>
> I've recently been having issues with upgrading packages with pear when
> xdebug is enabled.
>
> xdebug 2.1.0 (installed via pecl)
> pear 1.9.1
> php 5.3.2 (stock install via synaptic)
> ubuntu 10.04
>
>
> The symptom is basically that a bunch of php warnings are issued:
>
>
sudo pear upgrade Console_Getopt
>
> Warning: file_exists(): Unable to find the wrapper "channel" - did you
> forget to enable it when you configured PHP? in PEAR/Downloader/Package.php
> on line 1517
> PHP Warning: file_exists(): Unable to find the wrapper "channel" - did you
> forget to enable it when you configured PHP? in
> /usr/share/php/PEAR/Downloader/Package.php on line 1517
> PHP Stack trace:
> PHP 1. {main}() /usr/share/php/pearcmd.php:0
> PHP 2. PEAR_Command_Common->run() /usr/share/php/pearcmd.php:305
> PHP 3. PEAR_Command_Install->doInstall()
> /usr/share/php/PEAR/Command/Common.php:271
> PHP 4. PEAR_Downloader->download()
> /usr/share/php/PEAR/Command/Install.php:661
> PHP 5. PEAR_Downloader_Package->initialize()
> /usr/share/php/PEAR/Downloader.php:278
> PHP 6. PEAR_Downloader_Package->_fromFile()
> /usr/share/php/PEAR/Downloader/Package.php:160
> PHP 7. file_exists() /usr/share/php/PEAR/Downloader/Package.php:1517
>
>
> And after install:
> Warning: unlink(/tmp/glibctestZ7RpJW): No such file or directory in
> System.php on line 206
>
>
> Overall, it seems that the warnings are harmless, but it's a bit
> disconcerting to see.
>
> I came across this because phing was giving me some warnings coming from
> Net_Ftp, so I decided to try to upgrade thinking it might be a compatability
> issue with php 5.3. That's when I came across the issue. I had upgraded
> xdebug last week and the errors felt similar to what you'd get if
> xdebug.show_exception_trace is enabled. So I tried disabling xdebug, and the
> issues went away. I haven't been able to figure out if the problem is from a
> particular xdebug setting or if it's just xdebug in general. xdebug 2.0.5
> did not have any problems.
>
> I installed it via pecl and the settings are as follows:
> xdebug.scream => On => On
Hi David,
This setting will unsilence errors suppressed by the @ operator. I
would guess the warning is expected as the line in question uses the @
operator, but couldn't say for sure. Try disabling xdebug.scream and
the warnings should go away.
Best Regards,
--Matthew