================
@@ -4078,6 +4255,9 @@ void RegisterRequestCallbacks() {
g_dap.RegisterRequestCallback("threads", request_threads);
g_dap.RegisterRequestCallback("variables", request_variables);
g_dap.RegisterRequestCallback("disassemble", request_disassemble);
+ // Instruction breapoint request
----------------
walter-erquinigo wrote:
you could make something synthetic, and that could be very nice.
In the process event loop in lldb-dap, you could check if you stopped because
of a breakpoint, and then you check if the breakpoint is an instruction
breakpoint, and then you return that custom stop reason.
lldb-dap already does something like that in `CreateThreadStopped` for
exception breakpoints.
https://github.com/llvm/llvm-project/pull/105278
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
