I went looking at what was listening on that port with: sudo lsof -i:9000 sudo lsof -tnP -i:9000 | xargs -n 1 ps -p Local’s PHP service uses this setting which you can find in the site’s configuration file: site-name/conf/php/ The issue was likely hyper-specific to me (I think I messed something up on my system while testing PHP 8) but I’ll post what I did in case it helps someone else.īasically, Xdebug is usually configured to listen on port 9000. Nice! Thanks for the sanity check re-installed the latest version of PHPStorm and still had the issue, so I kept investigating. Mostly I wanted to gauge what PHPStorm users are doing and if I’m missing an easy configuration step. – I see that you commented on the above WI-56500 issue – Are you using the latest version of PHPStorm along with Xdebug + Local or are you doing something else?Īs a follow-up, I can advocate for upgrading Xdebug to the 3.x line, though I don’t know how quickly we’ll be able to get that updated.The specific version that worked for me was 2020.2.4Īfter doing some research, I found this bug report that’s closed, but it seems like the issue is still present: It was only when I downloaded an older version of PHPStorm that I was able to trigger the breakpoints that were being set. So basically, I couldn’t get the latest version of PHPStorm (2020.3.1) to work with the version of Xdebug in Local (currently version 2.9.0). Since PHPStorm isn’t my primary editor, I thought I was doing something wrong (and maybe I still am!) but I wanted to post my findings so that the Local community could help me get things figured out. Can I get some help to flesh out my understanding of Local+Xdebug and PhpStorm?
0 kommentar(er)
