Randy Fay

It seems to me like @mikesnoeren 's fixes have added up to complete success on this. Hope you agree @tyler36 , or we'll reopen. Congratulations @mikesnoeren !

Sounds fine. A PR against https://github.com/drud/ddev/blob/a57e03500f1ba96ac1bd456f922c236d6c20d06d/pkg/ddevapp/global_dotddev_assets/commands/web/xdebug would be easy to do and it's easy for you to test because you can just override the default command.

Somebody else hit that, not sure what's up with it, but * Make sure you have go 1.17 * `go mod vendor && go mod tidy` and see if that...

It looks like you have an ancient version of ddev source. Could you please update to the current version? I think that will help.

It's no surprise that you don't have xdebug in your ~/.ddev/commands/web I guess. It got moved there in the alphas. In your (v1.18.2? ) version it's in the project .ddev/commands/web...

Ah, sorry. I saw the /tmp/ddev path and thought it was a complaint from inside the container that we used to use for builds. No idea what's going on with...

@louis-cuny could you please review * https://github.com/drud/ddev/pull/3754 Thanks.

I'm going to close this for now; it's easy to test your update to the xdebug command by just editing it in ~/.ddev/commands/web and removing the #ddev-generated and getting it...

Thanks for this! I do hope you've seen `ddev xhprof` and `ddev blackfire`, which IMO are way better techniques for profiling than xdebug has ever provided.

Note that xdebug 2 is long in the rearview mirror and irrelevant. If we do anything, it will involve xdebug 3 only. Also, xdebug 3 is the only option in...