Vscode-php-debug: Anybody continuing the development of this extension?

[AnrDaemon]

Last commit to the repo is from March, and there's just too many bugs that block daily work.

[augustocdias]

Doesn't look like... There's 25 open pull requests and no comment on most of them

[zobo]

It's a shame, since this is a top match extension for when people search vscode and php debugging. Wonder if @felixfbecker would take a maintainer to at least comb over open PRs...

[austenc]

What are people using instead? I keep running into xdebug connection issues. It works, then it doesn't.. 🤔

[AnrDaemon]

It works reliable only if you keep only one session running. :/

[zobo]

Hm.. I did not have such cases yet... How is it unstable, how to reproduce it?

[AnrDaemon]

If you have 2 or more xDebug connections simultaneously opened in the same VS Code window, it's impossible to switch between them.

[cjwijtmans]

start an active fork then?

[AnrDaemon]

Not in a position to do so. Else I would.

It got better with VS Code 1.41+ though (SUDDENLY!). But changing between debugging sessions is still problematic.

[cjwijtmans]

The only annoyance i had so far is that i get breaks when an exception is being display with no traces then i get another break on the same exception with a trace(if the exception is not caught). So i get two breaks on the same exception unless the exception is caught then i get one break with no stack trace. So why not just get rid of the first break without a stack trace. Not sure what is causing this behavior though.

[AnrDaemon]

xdebug.remote_mode = jit ?
That's how xdebug itself works. Extension is only listening, it can't know ahead of time, what xdebug will send to it.

[cjwijtmans]

xdebug.remote_mode = jit ?
That's how xdebug itself works. Extension is only listening, it can't know ahead of time, what xdebug will send to it.

Not what i am saying. It appears that exception that are caught(later) are breaking with no stack trace. While exceptions that are not caught(later) are breaking once without stack trace and then again with a stack trace... So add an option to only break when there is a stack trace present. What causes this behavior, i have no idea.

EDIT:

https://xdebug.org/docs/all_settings

integer xdebug.show_error_trace = 0
Introduced in Xdebug >= 2.4

When this setting is set to 1, Xdebug will show a stack trace whenever an Error is raised - even if this Error is actually caught.

integer xdebug.show_exception_trace = 0
When this setting is set to 1, Xdebug will show a stack trace whenever an Exception or Error is raised - even if this Exception or Error is actually caught.

Error 'exceptions' were introduced in PHP 7.

Seems like normal behavior. The thing is this means you could ignore errors/exceptions with no stack traces and that way avoid breaking on things that are caught.

[AnrDaemon]

Why not disable breaking on caught exceptions?

Sadly it can't be set in "xdebugSettings": {…}.