Feature Request: Custom Breakpoints For Extensions

[smarr]

Hi:

I am currently exploring the options of using VS Code to build a debugger for an actor-based language.

One of the things that are key for the project are custom and often complex types of breakpoints.
In our current prototype, we support for instance the following types of breakpoints:

On the asynchronous message send operator, we can set a sender side or a receiver side breakpoint.

On method definitions, we can set breakpoints that are only triggered when that method is activated via an asynchronous message (but not when it is called synchronously).

Since this is probably far from a common requirement, I would also be more than happy with some recommendations of how I could prototype this myself.

While we have popovers in our prototype, the context menu might do (however, the 'when' clause in package.json does not seem to be taking callbacks for custom predicates?). A custom indicator/handle to interact with the breakpoint might still be nice (I think the decorator-sample comes with code that I can probably adapt).
And when the breakpoint is set, it needs to be communicated to the process that's debugged, but I'll probably be able to extend the debugging protocol to my needs.
So, I think, it should be possible for me to prototype something, but I'd be very grateful for guidelines and perhaps pointers to the most relevant elements that I should be aware of.

Thanks
Stefan

[smarr]

One element for the custom breakpoints that would be very useful is to have support for context menus that are specific to a token for instance: #11405

[vscodebot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!