PHP version: 5.6 / 7.0
XDebug version: 2.4.0
Adapter version: 1.7.1
Your launch.json:
{
"version": "0.2.0",
"configurations": [
{
"name" : "PHP Web Application : XDebug",
"type" : "php",
"request" : "launch",
"port" : 9000,
"serverSourceRoot" : "E:\\Development\\vps\\LeCoterie\\LeCoterie-Website"
}
]
}
XDebug is working, however when verifying how XDebug works within vscode-php-debug versus PHPStorm I see a difference which causes issues with Laravel.
Basically, when I debug via PHPStorm, Laravel is using a plethora of Vendor items, of which some throw exceptions which are handled within the backend of PHPStorm (Testing for RegEx, etc) and doesn't cause any issues.
When I debug via VSCode, the exceptions are caught and by doing so actually stops the application from running as expected.
I am not sure how PHPStorm does it, but would there be any way of excluding paths from debugging, or adding in Exceptions types to be excluded from debugging.
PHP version: 5.6 / 7.0
XDebug version: 2.4.0
Adapter version: 1.7.1
Your launch.json:
{ "version": "0.2.0", "configurations": [ { "name" : "PHP Web Application : XDebug", "type" : "php", "request" : "launch", "port" : 9000, "serverSourceRoot" : "E:\\Development\\vps\\LeCoterie\\LeCoterie-Website" } ] }XDebug is working, however when verifying how XDebug works within vscode-php-debug versus PHPStorm I see a difference which causes issues with Laravel.
Basically, when I debug via PHPStorm, Laravel is using a plethora of Vendor items, of which some throw exceptions which are handled within the backend of PHPStorm (Testing for RegEx, etc) and doesn't cause any issues.
When I debug via VSCode, the exceptions are caught and by doing so actually stops the application from running as expected.
I am not sure how PHPStorm does it, but would there be any way of excluding paths from debugging, or adding in Exceptions types to be excluded from debugging.