-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: Update documentation for xdebug 3 #539
Comments
This amounts to a support request, not a feature request, so closing. |
I'm confident the example in the docs works because I've used it myself. I did however spend some time reading the xdebug and php-debug-adapter docs, as it does seem a nontrivial debug adapter, and quite unusual. @przepompownia can you confirm? @cprn my recollection is that you need the chrome plugin (or something) to set some cooke that makes the xdebug thing actually break then refresh the page. If I remember correctly, The error about no threads is a common bug in many debug adapters, but is usually harmless. This is the exact configuration that I have used, and works in my environment. Your configuration may need to be different and you may have to read the docs of the third-party aspects here. Vimspector is not ever going to document third-party things like the debug adapters, and how to make them work, because I am just 1 guy in my spare time and there are literally hundreds of them, and thousands of users. |
Example provided by you is for version I don't think I need any browser plugins when running PHP process in CLI (as far as I can tell this config just runs
Should I ask on one of the chats listed in the new issue form? |
Well it took me all of 5 minutes to make it work by following the xdebug installation instructions, and then the vscode-php-debug instructions.
|
OK, this I did not expect. It doesn't work with Xdebug installed from repository but works when it's installed from PECL. I'll investigate further but it seems it should be solved by the package maintainer. Thank you for your help. I wasted so many nights. 🤦♂️ |
you're welcome. for the record I have no clue what pecl is, I just did what the instructions told me to! |
@puremourning Indeed, it would be good to show some minimal XDebug 3 configuration too, e.g. xdebug.show_local_vars=on
xdebug.discover_client_host = false
; override with XDEBUG_CONFIG="client_host=192.168.42.34 client_port=9004"
xdebug.client_host = localhost
xdebug.client_port = 9003
xdebug.log=/tmp/xdebug.log
xdebug.mode=debug
xdebug.start_with_request=trigger @cprn to eliminate the adapter (vscode-php-debug) and the client possible issues, you can try to use CLI DBGP client with
It's hard to say, given XDebug as the only point of reference 😉 |
Is your feature request related to a problem? Please describe.
I cannot manage to run Vimspector with Xdebug3, it runs PHP without stopping on breakpoints, displays correct output and shows
Protocol error: Server returned no threads
each time. I went through documentation back and forth and failed to notice whatever I'm missing. Google doesn't find working examples either.Describe the solution you'd like
I'd like a working example in documentation.
Describe alternatives you've considered
I tried with several combinations of Xdebug settings but didn't manage to find a working one.
Additional context
Versions:
Vimspector installed with
vim-plug
without issues.test.php
- file to runvscode-php-debug
on:.vimspector.json
:xdebug.ini
:Vimspector log:
Screenshot:
The text was updated successfully, but these errors were encountered: