0

I have a strange behavior with my VSCode debugger. I had to update my docker desktop and it nuked all my containers. after updating,reinstalling and setting up my Laravel containers my XDebug breakpoints only work at the route level ie- the api.php level. I can set breakpoints and all is well...but if I set any breakpoints in any controllers I get "Error:socket hang up" in postman. On chrome the connection closes with error:ERR_EMPTY_RESPONSE in the network inspector and the API call fails. It smells like a timeout somewhere but I cannot find it.

launch.json looks like this:

"configurations": [
  {
      "name": "Listen for Xdebug",
      "type": "php",
      "request": "launch",
      "port": 9003,
      "log":true,
      "pathMappings": {
            "/var/www/html": "${workspaceFolder}"
        },
        "hostname": "0.0.0.0",
  },
  {
      "name": "Launch currently open script",
      "type": "php",
      "request": "launch",
      "program": "${file}",
      "cwd": "${fileDirname}",
      "port": 9003,
  },

]

my php.ini :

[Xdebug]
xdebug.mode=debug
xdebug.start_with_request=yes
xdebug.client_port=9003
xdebug.client_host=127.0.0.1
xdebug.discover_client_host=1
xdebug.var_display_max_depth=10
xdebug.idekey = XDEBUG_VSCODE

I have the XDEbug plugin for chrome running and set the IDEkey to match XDEBUG_VSCODE. I also have the php-debugger plugin running in VSCode. Totally confused.

php -v output

Improve this question
Related questions
0
Eclipse 3.0 for php not stopping at breakpoint,
988
How do you format code in Visual Studio Code (VSCode)?
865
Run / Open VSCode from Mac Terminal
Load 3 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.