exceptionInfoRequest never fires

[theIDinside]

Does this issue occur when all extensions are disabled?: Yes. Only one extension running, custom debug adapter.

• VS Code Version: 1.67.2
• OS Version: Ubuntu 22.04

Steps to Reproduce:
For the debug adapter response.body.supportsExceptionInfoRequest = true;

When an exception happens, send sendEvent(new StoppedEvent("exception", threadId))

Never reaches exceptionInfoRequest for the inline debug adapter implementation.

[theIDinside]

It seems to have been fixed by this issue #113921 - however, as stated, doing the above does not trigger exceptionInfoRequest to be called.

Setting a breakpoint in it, or override dispatchRequest one can see that exceptionInfo command is never sent.

So it seems there is some hidden state that needs to be set for it to work. What could that hidden state be, I wonder?

[theIDinside]

So I've solved it.

If the source can't be found for the focused stack frame, exceptionInfoRequest will not fire at all.

And it's not documented anywhere either, that the "focused" stack frame from a stackFrameRequest is the "first one with source != null so these are two things the VSCode team should seriously consider documenting.

In C++ the actual "exception" for an uncaught exception is just a signal of SIGABRT (or std::terminate) - these will not be in the workspace folder of any workspace (most likely) thus, as a debug adapter, returning the source file names for these, will make VSCode say "it can't open foo".

I suggest adding documentation for these things.

[roblourens]

Sorry for the slow response. Since the exception info is shown in the vscode editor, then if the source can't be loaded in an editor, where do you expect it to be shown?

exceptionInfoRequest will be called when the UI needs it- I don't think we can document any guarantees about exactly when it will be called, and the DA shouldn't make assumptions.

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!