Closed 8ctopus closed 4 years ago
martomo
commented
4 years ago It seems you commented out Notice instead of Warning in the break_on_exception configuration.
You could try the following, which does not break on both Notice and Warning exceptions:
"break_on_exception": [
"Fatal error",
"Catchable fatal error",
"Parse error",
"Strict standards",
"Deprecated",
"Xdebug",
"Unknown error"
],
8ctopus
commented
4 years ago Hi @martomo, thanks for the quick reply.
If I comment both notices and warnings, all works fine. If I comment only notices or use the default array (notices enabled), I can't get past line 12, I get the same warning every time I "Step Over", "Step Out", ...
I tested the same config in Visual Studio Code and it behaves the same as with Sublime Text / xDebug Client. And I found this thread on stackoverflow.
The conclusion is that it is not to be related to the plugin itself but to the way errors are managed in php7. Solution being to comment warnings.
Thank you for taking the time.
The debugger is stuck on a warning without possibility to proceed further. All works fine is I comment Warning in the break_on_exception array. The database password is intentionally incorrect for the demonstration.
The bug is easy to reproduce in this github project. Git clone the project, docker-compose up then start debugging and open url http://localhost:8000/connect-to-database.php (change password to 1234 to get the warning).
Environment
Sublime Text
Windows 10 Pro Sublime Text 3.2.2 Build 3211 Xdebug Client 1.1.2 Python 3.3.6 (default, Mar 29 2018, 23:30:25) [MSC v.1600 64 bit (AMD64)]
Server
Operating system: Alpine Linux in docker PHP/Xdebug version: php 7.3.16 xdebug 2.9.1
Configuration
php.ini/xdebug.ini
Packages/User/Xdebug.sublime-settings
*.sublime-project
Logs
Console output:
Packages/User/Xdebug.log: