Debugging with VS code seems impossible

VictorVadillo

Hello,

We are testing for small Wordpress and Prestashop projects the usage of VS CODE + PHP Tools for VS under WSL.

All is installed and working, extension is properly loaded, and we can start debug without problems, and stop in breakpoints.

We are using this configuration for Xdebug 3:

zend_extension=xdebug.so
xdebug.mode=debug
xdebug.start_with_request=trigger
xdebug.discover_client_host=1
xdebug.client_port=9003
xdebug.client_host=127.0.0.1
xdebug.idekey=VSCODE

We are sending XDEBUG_SESSION_START=vscode in the URL to start debugging, and as I mention before, all seems OK.

We can step forward, over, etc. but sometimes, with random variables, debugging is not stopped, but the executing line is missing, we can not step forward again, variable content cannot be evaluated, etc.

Seems like the execution is stopped but VS code has missed the connection with debugger, line is not highlighted, etc.

The majority of times this occur positioning the cursor over a variable to see the contents.

JakubMisek

Hello Victor,

Thank you for the detailed information.

As I understand, the debugging of a request initially works. But at some point, maybe after a mouse hovering over a variable, the debugging of the current request stops working?

We are currently working on a fix that might be responsible for this.

VictorVadillo

Exactly,

Seems that hot evaluation and/or watch evaluation of variable breaks debugging.

Do you have an ETA for this fix?

JakubMisek

I see; ETA is this week

1/ it would help us to see Xdebug log. You can enable Xdebug 3 log by adding the following to your php.ini

xdebug.log="logpath.log"

2/ Do you have anything in your Watch window?

Thank you

VictorVadillo

Hello,

Debug log enabled but no file is generated, maybe I'm missing something.

The problem happen randomly, with or without variables in Watch

JakubMisek

The log would really help because we are already handling all the problems we're aware of.

The log path should be an absolute file path, with write access.

xdebug.log="c:\xdebug.log"

VictorVadillo

Hello,

Finally I managed to create debug log.

I am under windows linux subsystem, so are linux permissions problem.

Attached you will find the file https://pastebin.com/nWcr5D4T

JakubMisek

Thank you, and did the error happen while creating this log?

VictorVadillo

Hello,

Yes, it happens continously. Then, I must restart the process. Currently I am debugging an import process, and I must delete manually all imported data to start over again.

JakubMisek

Today's release fixes most of the debugging issues. Please try the update (version 1.2.6549) and let us know if it helps.

Thanks!

VictorVadillo

No, I'm sorry.

Not solved.

VictorVadillo

Can I provide you some additional information and / or debugging?

JakubMisek

Hello Victor, thank you for the feedback,

We're keeping working on it, although the latest update fixes another bunch of issues.

May I ask you to try the latest version (1.3.6616)

Thank you

VictorVadillo

Hello, after testing intensivelly, I see that the bug has been solved.

Thank you!

JakubMisek

Thank you Victor for letting us know!