Closed antivanity closed 1 year ago
If i hit F5 and then do the command "Developer: Restart Extention Host" the debugger connects immediately and works.
So maybe another extention is causing problems. Still digging.
Interesting that there is noting in the logs. Try different ports to exclude that... Do you see anything in the proxy logs on the "remote" host?
Problem was caused by gitlens for some reason, i disabled it and your plugin is working again.
Gitlens error:
2023-07-13 19:09:56.216 [error] TypeError: t.trim is not a function at new RunError (c:\Users\mycomp\.vscode\extensions\eamodio.gitlens-14.1.0\dist\gitlens.js:1:295302) at c:\Users\mycomp\.vscode\extensions\eamodio.gitlens-14.1.0\dist\gitlens.js:1:296499 at ChildProcess.exithandler (node:child_process:417:5) at ChildProcess.emit (node:events:513:28) at maybeClose (node:internal/child_process:1121:16) at Socket.<anonymous> (node:internal/child_process:479:11) at Socket.emit (node:events:513:28) at Pipe.<anonymous> (node:net:757:14)
Thanks for taking a look, feel free to close this ticket.
PHP version: 5.6.4 Xdebug version: v2.5.5 VS Code extension version: 1.32.1
Your launch.json:
VS Code extension logfile (from setting
"log": true
in launch.json): No output at all in debug consoleWhats going on: This was working recently last week on my machine. My co-workers xdebug works..
I click the debug play button, nothing happens, no output to debug console. Same with F5, or any other way of telling it to start debugging.
Try "Debug: Restart", and i get a "forever loading" status bar in the debugging side panel.
Iv deleted my launch.json file, recreated it, restarted my computer, restarted vscode, tried different versions of xdebug plugin, im at a loss at this point.