GotoTargetsArguments should have thread id about debug-adapter-protocol HOT 3 OPEN

Note: You have a screen shot of VS, but I don't think VS could provide you that information (at least not without a bunch of work) even if a thread id was added to the protocol as at the time that the UI asks the engine for the corresponding engine API (IDebugProgram2.EnumCodeContexts]) it doesn't know a thread.

Is there a problem with just failing the goto request instead?

from debug-adapter-protocol.

It's what we're doing currently, so this is mostly about better UX.

It seems that most DAP implementations should be able to provide the thread in these circumstances, since they are issuing a goto request with that information immediately after. So I think it would be nice to have it in the protocol at least as an optional field, to encourage future implementations to provide it. The adapter can then try to do the best it can based on the information it has.

from debug-adapter-protocol.

For the screenshot below, I forced a blank targets response. This allows IDE to show changes to cursor indicating the move invalid

An extension of this is described in https://blog.jetbrains.com/idea/2020/08/jump-to-any-line-while-debugging/ (Limitations paragraph). They apparently color the lines based on how dangerous it is to jump to that line.

from debug-adapter-protocol.