Support for multiple debug adapter clients for the same session at the same time

[Smjert]

Hello everyone, is my understanding correct that codelldb does not support having multiple clients for the same debugging session?
With clients I mean, one is the VSCode extension, which drives the debugging session, and then a second process which can just query the state (to not desync the debugging session), to maybe do some visualizations.

I know that codelldb has its own python API to do some visualization in for instance HTML, but I'd like to be independent from vscode or codelldb specifically (basically only speak DAP).

If that wasn't the case, I thought of interposing myself with another process between the extension and codelldb, and do some multiplexing, but as far as I can see the extension has no custom path exposed for the codelldb binary too.

I know it might be a bit of niche question (and wasn't sure this was also Issues worth yet), but if one cannot do the first, and especially the second, any chance the extension can expose a way to change the codelldb path?

Or is there another way I haven't thought about?

[vadimcn]

It's possible to monitor any DAP session, including CodeLLDB, via DebugAdapterTracker. One can also inject messages via DebugSession::customRequest. For an example of extension that does this, see Debug Visualizer.

[Smjert]

Hello @vadimcn thanks for your answer!
I half forgot about that extension after having seen it two days ago 🤦‍♂️; I think i forgot because I was trying to avoid having to integrate with VSCode.

In any case, I'll try this; if what comes through that APIs is still the same DAP message sent by either the editor or the debugger, then a thin layer in VSCode to send that to an external process is doable.