Mathias Fußenegger

You could write some custom functions that let you export and import the active breakpoints: ```lua local breakpoints = require('dap.breakpoints') function M.store() local bps = {} local breakpoints_by_buf = breakpoints.get()...

> At least for the life of the current open file. This is currently already the case, or maybe I misunderstand what you mean with persisting?

> From the UI point of view: mapping dd (or anything configurable) on a single quickfix item to remove breakpoint would be a significant step ahead. I'd kinda like that,...

How does the disassembly functionality with codelldb look like? There is a disassemble request in the protocol: https://microsoft.github.io/debug-adapter-protocol/specification#Requests_Disassemble It takes a memoryReference, which I assume has to be taken from...

See also https://github.com/vadimcn/vscode-lldb/pull/627, looks like standard DAP conform disassembly request isn't supported yet in codelldb

Wasn't this fixed in https://github.com/mfussenegger/nvim-dap/issues/343 ? Do you know which process isn't terminated? the debug-adapter or the debugee? Terminate shouldn't even be required, according to the specification if you're using...

I'm also not sure what else nvim-dap could be doing. The `launch` request doesn't have any response - so nvim-dap doesn't know the `pid` of the process that gets started...

Could be that it doesn't set the `terminateDebugee` option if you call `dap.terminate` like that. Did you try with ```lua dap.terminate(nil, nil, function() -- start next debug session here end)...

Do you think you could create a minimal project and a minimal reproduction so I could look into it?

I think the problem is that many parts of `run` are async. The session gets assigned before it is fully initialized. So the second `terminate` doesn't work because the just...