Echo, var_dump, exit, and die. Try xdebug + sublimt debugging today and find that it is not easy to use. You are debugging this way. Are we all using var_dump for php debugging? Echo, var_dump, exit, and die. Try xdebug + sublimt debugging today and find that it is not easy to use.
You are debugging this way. Are we all using var_dump for php debugging?
Reply content:
Echo, var_dump, exit, and die. Try xdebug + sublimt debugging today and find that it is not easy to use.
You are debugging this way. Are we all using var_dump for php debugging?
xdebugJust configure a regularIDEOtherwise, usegdbThere is no difference. OnePhpStormAnd so on.IDE, Breakpoint, step, and variable details are all very simple operations.echo,var_dumpIt is much easier to debug this kind of guess.
I used this for debugging.BeaverHttps://github.com/funcuter/beaver
Echo, var_dump, exit, die ()
It is not a particularly complex application. Small websites are enough,
Chromephp plug-in & chromephp. php class library
Https://github.com/ccampbell/chromephp
Download ChromePhp. php
Create a PHP file, such as 1.php
include 'ChromePhp.php';ChromePhp::log('Hello console!');ChromePhp::log($_SERVER);ChromePhp::warn('something went wrong!');
Chrome app store installs the chromephp plug-in (please refer)
Open a new tab and light up the chromephp plug-in.
Enter a URL and you will see the debugging output under the chrome development tool console tab. My results
Use phpstrom, which has powerful debugging functions, such as power-off debugging. My favorites.