xdebug

I'm kind of new to using Homebrew, but I love it. It's so easy. I'm trying install Xdebug. Some of the posts on the web say to do this: brew install xdebug But it doesn't work. I get: Error, no available formula. I did brew search xdebug and it returned: josegonzalez/php/php53-xdebug josegonzalez/php/php54-xdebug I tried several different iterations of brew install with this including brew install php53-xdebug , but still no luck. Can someone help me? I can't find anything on Xdebug's site about using Homebrew, but yet posts on the web seem to indicate it's possible. Germain Carré Add this

New to PHP. Working on a PHP project and have xdebug enabled to be able to debug my php applications. The production server does not have xdebug enabled because it is handled by another team. On my local machine, when I run composer it gives me a warning saying You are running composer with xdebug enabled. This has a major impact on runtime performance. I do not want to disable xdebug when I am developing. Just wanted to confirm that running xdebug in dev environment should have no impact on the composer installing libraries/performance of the app on the production server. I do not want to

When running composer diagnose , I get the following error : The xdebug extension is loaded, this can slow down Composer a little. Disabling it when using Composer is recommended. How can I disable xdebug only when I'm running Composer? Update : The issue has been fixed in Composer 1.3 . Update composer to the latest version by executing composer self-update , instead of trying the following workaround. Here is my modification of @ezzatron's code. I have updated the script to detect ini files from phpinfo output. #!/bin/sh php_no_xdebug () { temporaryPath="$(mktemp -t php.XXXX).ini" # Using

I have managed to initiate php-cli script debug session from the IDE itself, but I need to start the debugging session from the shell / command line. These are rather complex maintenance PHP scripts which take a lot of input parameters, so entering arguments from within Netbeans is a bit cumbersome. I have done it before with Zend studio: https://zend18.zendesk.com/hc/en-us/articles/203838096-Debugging-PHP-CLI-Scripts , but now I need to get it working with Netbeans. Thanks in advance. Andrew Hancox I got this working on Ubuntu/Netbeans by: copying the xdebug config lines from the /etc/php5

Preamble Like many, I've spent more hours debugging my IDE’s connection to XDebug than I have using XDebug to debug my programs. I’ve gotten it to work repeatedly , but every once and a while I get the common “Waiting to connect” problem . I haven’t been able to localize what causes XDebug to work or fail. I’ve been using ubuntu for two years; I’m neither a noob nor an strace guru. What am I doing wrong? How can I better debug my IDE’s connection to XDebug? Setup Ubuntu 10.10 Netbeans 6.9.1 PHP 5.3.3-1ubuntu9 with Suhosin-Patch Xdebug v2.1.0 with debugclient built Sep 20 2010 from source using

I sometimes prefer to use header("Content-type: text/plain"); Do not mess around with HTML. However, whenever an error occurs, or when I use var_dump() , it would issue a large HTML block to prettify the output. While it's great in HTML context, I would like to disable it when I work in text/plain. Is it possible to do? Runtime disable of the prettify? Bere XDebug will show you an error if PHP HTML errors are enabled. You can do one of the following You can disable php errors from displayed. ini_set('display_errors', 0) Or you can change html_errors = On setting of php.ini for xdebug to html

I'm programming PHP for some time. I use an Windows XP SP3 with PHP 5.4 , SQlite 3 , Apache 2.4 as a development environment. The remote host server (not mine) is a Windows Server 2008 with PHP 5.3 , Apache 2.2 , IIS 7.0 and SQL Server 2008 . My editor is the simple and wonderful EditPlus . Concerning Javascript it's nice because of Firefox plus the great add-on FireBug , which allows for complete HTML + CSS + Javascript debugging. My problem is PHP error management in my development environment (my personal machine). The PHP syntax errors typically appear ok with line number and so on,