@@ -33,7 +33,7 @@ int main(int argc, char const *argv[]) {
if (foo == nullptr) {
fprintf(stderr, "%s\n", dlerror());
exit(2);
- }
+ } // end of foo check
SLTozer wrote:
I can make this change, but other comments used for setting breakpoints in the
https://github.com/SLTozer updated
https://github.com/llvm/llvm-project/pull/149133
>From 773cff4106a9c28300847fcc9612ea25cc0cd44d Mon Sep 17 00:00:00 2001
From: Stephen Tozer
Date: Wed, 16 Jul 2025 17:06:39 +0100
Subject: [PATCH 1/2] [lldb-dap] Allow returning multiple breakpoints in
"stopped
https://github.com/SLTozer edited
https://github.com/llvm/llvm-project/pull/149133
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -33,7 +33,7 @@ int main(int argc, char const *argv[]) {
if (foo == nullptr) {
fprintf(stderr, "%s\n", dlerror());
exit(2);
- }
+ } // end of foo check
SLTozer wrote:
This comment is being used to set the breakpoint from
[here](https://github.co
@@ -173,6 +173,29 @@ def verify_breakpoint_hit(self, breakpoint_ids,
timeout=DEFAULT_TIMEOUT):
return
self.assertTrue(False, f"breakpoint not hit,
stopped_events={stopped_events}")
+def verify_all_breakpoints_hit(self, breakpoint_ids,
tim
https://github.com/SLTozer created
https://github.com/llvm/llvm-project/pull/149133
Currently, the "stopped" event returned when a breakpoint is hit will always
return only the ID of first breakpoint returned from
`GetStopReasonDataAtIndex`. This is slightly different from the behaviour in
`l
SLTozer wrote:
The approach sounds reasonable enough to me that it's probably best to open a
PR and continue discussion there - the C API is a bit of a special case, so it
might warrant bringing in people who know more about it (and actually consume
it) if a change is necessary, but I suspect
