Would it be possible to provide information in the response of run commands invoked about the breakpoint that was hit (in cases where the debugger is breaking due to a breakpoint)? Currently, the response only contains the text "break" in the status string of the base DBGp protocol. This lets clients know that a breakpoint was hit, but not necessarily which one or of what type it was.

Some reasoning for this:

I'm in the process of integrating Xdebug support into the Nova IDE, which will support additional UI "actions" on each breakpoint that can be invoked when that breakpoint is hit. These are actions like "play a sound", "log a message", "invoke a debugger command". Things that the Xdebug / DBGp protocol don't need to handle in any way.

But, in order to make them work, I'd need knowledge of which breakpoint caused the run to stop. Given a line breakpoint, it's possible to check to see which are set on or near that line to infer which it might be, but with a call / return breakpoint there doesn't seem to be a good way to infer such information.

I believe that the breakpoint ID alone would likely be enough for this, but if in addition the breakpoint type was provided as well, it might be useful.

If this is actually already possible, please excuse my missing it. I examined the responses of the run command as well as the rest of the DBGp protocol and haven't yet found a good way to do this.

Thank you for considering!