#php: get your hands on phpdbg: phpdbg.com v0.0.1 released :) #phpdbg


Four years ago to the day, #phpdbg was born ... where's our birthday cake ? #php


#phpdbg just got an upgrade: an XML protocol for IDEs, some improvements ... and was ported to PHP 7! #PHP


previous my tweet is a code snippet for #phpdbg


Swapped #xdebug code #coverage to #phpdbg with huge speed up. From 3.36 minutes, Memory: 34.00MB to 13.29 seconds, Memory: 118.00MB. Only had to set memory limit #docker #gitlab #php

pionl's tweet image. Swapped #xdebug code #coverage to #phpdbg with huge speed up. From 3.36 minutes, Memory: 34.00MB to 13.29 seconds, Memory: 118.00MB. Only had to set memory limit #docker #gitlab #php

phpdbg - The interactive PHP debugger -github.com/krakjoe/phpdbg - IRC: #phpdbg on EFnet :) #php #debugging


Pushed new #phpdbg features to #PHP just now! Included are watchpoints and a lot of bug fixes. Just in time for PHP 5.6 beta 2.


There are #XDebug, #PHPDBG and DBG by #NuSphere. Distributed #PHP debugging capabilities in 5.6+ should take the best from all three.


I am wondering how #phpdbg compares to #XDebug and #DBG by #NuSphere.How does it internally work?Exposes static members?Not much resources..


#PHP needs officially supported debugger - even more than JIT. #PHPDBG cannot integrate with IDEs and no windows support, #XDebug is slow.


#phpdbg .phpdbginitようの関数 static PHP_FUNCTION(phpdbg_break) とstatic PHP_FUNCTION(phpdbg_clear) しかない、、


Use #phpdbg instead of #xdebug to generate your #PHPUnit code coverage, in my case it's 8x faster. #protip


PHP's built-in debugging tools are a kinda...😐 @mchojrin takes us on a tour of the top three debuggers for PHP to help you decide which is right for you!😎 #php #debugging #phpdbg honeybadger.io/blog/php-debug…


Swapped #xdebug code #coverage to #phpdbg with huge speed up. From 3.36 minutes, Memory: 34.00MB to 13.29 seconds, Memory: 118.00MB. Only had to set memory limit #docker #gitlab #php

pionl's tweet image. Swapped #xdebug code #coverage to #phpdbg with huge speed up. From 3.36 minutes, Memory: 34.00MB to 13.29 seconds, Memory: 118.00MB. Only had to set memory limit #docker #gitlab #php

Four years ago to the day, #phpdbg was born ... where's our birthday cake ? #php


Retweeted Romain Neutron (@romainneutron): Use #phpdbg instead of #xdebug to generate your #PHPUnit code... fb.me/43y8RlHN0


Use #phpdbg instead of #xdebug to generate your #PHPUnit code coverage, in my case it's 8x faster. #protip


#PHP needs officially supported debugger - even more than JIT. #PHPDBG cannot integrate with IDEs and no windows support, #XDebug is slow.


Added 'Generating Code Coverage with #PHPUnit and #phpdbg ‘ by @eminetto to #PHPreboot September magazine. #PHP phpreboot.com/magazine/sep16


Speeding up unit test suite with coverage of at least 65% by using #phpdbg instead of #xdebug! Reported results are quite equal! Yay! #php


@krakjoe Hi, will #PHPDBG be ever officially supported on Windows? Is it suitable to integrate into PHP IDEs? Does it work with #PHP7 ? thnx


I can't go and listen to @LGnome talk about #phpdbg at phptek, but you all should, if you can #php


@seldaek @Ocramius It just doesn't work if the binary is actually #phpdbg. /cc @bwoebi


Also here is the link to the vagrant box running #php 5.6, #xdebug and #phpdbg I used during my #phpse talk: github.com/belanur/php-de…


I was eager to have #phpdbg in my Ubuntu 14.04 using php5.5. I didn't realize I needed to build PHP sources a task which failed. Bison lib?


@krakjoe Heya! where's the #phpdbg irc channel? i see the link on the page but it does zilch


Swapped #xdebug code #coverage to #phpdbg with huge speed up. From 3.36 minutes, Memory: 34.00MB to 13.29 seconds, Memory: 118.00MB. Only had to set memory limit #docker #gitlab #php

pionl's tweet image. Swapped #xdebug code #coverage to #phpdbg with huge speed up. From 3.36 minutes, Memory: 34.00MB to 13.29 seconds, Memory: 118.00MB. Only had to set memory limit #docker #gitlab #php

Loading...

Something went wrong.


Something went wrong.


United States Trends