Debugging with Debug and PhpStorm
summary
A live demo reproduces a bug in a small Markdown blog with five posts where an unfinished article still appears; using Xdebug extension plus a browser extension sets XDEBUG_SESSION cookie and PhpStorm listening on 9000/9003 allows setting breakpoints, conditional breakpoints, inline watches and evaluate-expression checks without changing code. Stepping through the map/filter pipeline reveals a mapping typo that turns the hidden flag into a different key, fixing it removes the unwanted post so the list drops from five to four.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:33Debugging approaches in PHP
- 3:17Setting up Xdebug
- 7:11Starting debugging in PhpStorm
- 13:25Xdebug vs dump and die
- 14:29Advanced breakpoints in PhpStorm
- 21:13Debugging unknown code paths
- 23:00Xdebug vs other tools
- 24:23Closing remarks
related talks
58mDrupal Development with PHPStorm and Xdebug
49mSaving Time by Using a Debugger
54mDebugging Effectively
22mWhat's New in Xdebug?
50mMy Debugging And Performance Toolbox
59mGetting the most out of PHPStorm for Drupal 8
39mWhat's coming in PhpStorm
39mPHP for Pirates: pillaging interactive debugging from Ruby and JavaScript