PHP Debug in Visual Studio Code breaks on every exception

Question

I am just starting to use the PHP Debug extension in Visual Studio Code (Ubuntu 14.04). It mostly works fine for me, but I have a problem that every time an exception is thrown, the debugger automatically breaks. We have lots of exceptions which are internally caught and handled in our code, so I don't want to have to step through each of these.

I've been trying to find something like the Exception Settings in Visual Studio 2015, but can't find any equivalent options within Visual Studio Code.

php.ini settings:

[debug]
xdebug.remote_autostart=on
xdebug.remote_enable=on
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_host=localhost
xdebug.remote_port=9000

Visual Studio Code launch.json:

{
   "version": "0.2.0",
   "configurations": [      
       {
           "name": "Launch currently open script",
           "type": "php",
           "request": "launch",
           "program": "${file}",
           "cwd": "${fileDirname}",
           "port": 9000,
           "args": ["some arguments"]
       }
   ]
}

Note that when I use Netbeans for debugging with the same xdebug settings and the same codebase, there is no break-on-exception behaviour, so I think this must be something in Visual Studio Code and/or the PHP Debug extension.

Can anyone suggest how to pass through exceptions without breaking?

geekydel · Accepted Answer · 2017-06-14 07:32:26Z

39

I've just found the answer myself (feeling a little stupid now!).

In Visual Studio Code, go to View->Debug, then uncheck the 'Everything' button in the Breakpoints section. That option will automatically break on PHP Notices, Warnings and Exceptions.

answered Jun 14, 2017 at 7:32

geekydel

8357 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Thiago Barcala Over a year ago

+1 If it makes you feel less s*, I felt s* too... I had to omit the s* word, cause Stack Overflow thought my comment wasn't constructive.

Sarah Groß Over a year ago

You should accept your own answer! I feel stupid now for not having seen those options! ;-)

Evil Buck Over a year ago

doh! I missed them too! Thanks for leaving this answer.

jerclarke Over a year ago

I love you all and thank you and I'm sorry we are all such doofuses lol

jerclarke Over a year ago

For bonus points I had already left a detailed and embarassing GitHub Issue on the library I was using! Do I win the doofus olympics?

jpenna · Accepted Answer · 2019-03-01 10:08:24Z

4

I was looking for another answer for this question

I was having breakpoints in my Composer dependencies, which turned debugging really annoying.

For anyone having the same issue, you can set the property ignore in the launch.json file, with an array of glob patterns for the PHP Debug extension to ignore.

{
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Listen for XDebug",
      "type": "php",
      "request": "launch",
      "port": 9000,
      "ignore": [
        "**/vendor/**/*"
      ]
    },
    {
      "name": "Launch currently open script",
      "type": "php",
      "request": "launch",
      "program": "${file}",
      "cwd": "${fileDirname}",
      "port": 9000,
      "ignore": [
        "**/vendor/**/*"
      ]
    }
  ]
}

answered Mar 1, 2019 at 10:08

jpenna

9,2995 gold badges32 silver badges40 bronze badges

2 Comments

Juanmi Sosso Over a year ago

This is just what I was looking for. A way to tell Xdebug to ignore exceptions in some directories. Thanks.

Daan van den Bergh Over a year ago

For me it was the skipFiles parameter that did the trick. Same array, different parameter.

saber tabatabaee yazdi · Accepted Answer · 2020-05-02 21:54:35Z

4

follow these steps as image below then

check and unchecked what you want

answered May 2, 2020 at 21:54

saber tabatabaee yazdi

4,9953 gold badges53 silver badges63 bronze badges

Comments

Jonathan Williams · Accepted Answer · 2022-02-15 17:55:08Z

0

If the breakpoint options mentioned in other answers (notice, warnings, ...) are missing from the breakpoints panel in VSCode you may have attached a second debugger (like chrome) that removed them. Either attach xdebug last, or by itself.

answered Feb 15, 2022 at 17:55

Jonathan Williams

11 bronze badge

Collectives™ on Stack Overflow

PHP Debug in Visual Studio Code breaks on every exception

4 Answers 4

5 Comments

2 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

5 Comments

2 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related