Rascal Exception Breakpoint #2543
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a first implementation for DAP exception breakpoint.
It define a "Rascal Exception" breakpoint in the DAP :

When activated, instead of simply displaying the exception to REPL, it stop the evaluator on the exception and trigger a breakpoint with exception information. The exception message is displayed inline at the location of the exception :
Since the evaluator is stopped, the context of the exception is still accessible (e.g. variables). When #2523 will be merged, the user could interact with the evaluator in this suspended state.
When the debugger is resumed, the exception is then displayed in the REPL.
TODO/Question :