8/22/2023 0 Comments Ioncube decoder 10![]() The above shows that Xdebug is loaded first and OPcache second, which the documentation says you shouldn’t do:Ĭan be loaded together with Xdebug, but it is not 100% compatible. When I had another good look at the phpinfo() output from the user, I noticed: Zend Engine v4.2.8, Copyright (c) Zend Technologies with Xdebug v3.2.2, Copyright (c) 2002-2023, by Derick Rethans with Zend OPcache v8.2.8, Copyright (c), by Zend Technologies On my side (Linux, PHP 8.1/8.2) with php -S the behaviour was always correct, with the breakpoints resolved for each request through the dev server. I spent some time delving into this, and initially I could not reproduce this. Sometimes it also means it moves them to a line with executable code on it, as in some cases, PHP is “confused” about where lines of code live. Xdebug “resolves” breakpoints when it sees code compiled by PHP and then notifies IDEs that the configured breakpoints are valid. A user noticed that configured breakpoints in the editor would be greyed out for any request besides the first one for each process when using PHP’s built-in web server. ![]() Last week, the author of the PHP Debug Adapter for Visual Studio Code asked me to look at an issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |