Breakpoints not hit in CLion

[mgalindo-sc]

Description of the bug:

Hi,
When debugging tests in CLion (Build #CL-251.27812.15, built on July 22, 2025) breakpoints are not hit. This happens whenever triggering a debug session with a fully cached build (note the test runs, just the breakpoint is not hit).

Which category does this issue belong to?

No response

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

1. Open a test source and place a breakpoint where you know it will be hit
2. Debug the test using bazel (this will work fine)
3. Make a trivial change to the test source code to invalidate the cache
4. Debug the test again with bazel (this will work fine)
5. Revert the code change back to the initial step
6. Debug the test with bazel agains (the breakpoint will not be hit)
   After this point the breakpoint will no longer work in any of the two code states. The only way to get out of this state is to make a new change to the code to invalidate the cace.
   I've uploaded a couple of logs when it works vs when it does not work. Below I pasted a response from lldb that only appears in the log that works. In both cases the breakpoint is sent to lldb, but only in once instance lldb acks succesfully.

breakpoint {
    id: 1
    orig_file_path: "/Users/mgalindo/Snapchat/Dev/mobile/client/src/bitmoji/bitmoji_metrics/test/BitmojiMetricsTests.cpp"
    orig_line: 73
  }
  location {
    id: 1
    addr: 18446744073709551615
    is_resolved: false
    file_path: "src/bitmoji/bitmoji_metrics/test/BitmojiMetricsTests.cpp"
    line: 73
    module_path: "/Users/mgalindo/Snapchat/Dev/.cache/bazel/arm64/8c8755d317b4e4dbecf0ec0141efbb16/execroot/snap_client/bazel-out/darwin_arm64-dbg/bin/src/bitmoji/bitmoji_metrics/test"
  }
}

breakpoint_hit.log
breakpoint_not_hit.log

Which Intellij IDE are you using? Please provide the specific version.

2025.1.4 Build #CL-251.27812.15, built on July 22, 2025

What programming languages and tools are you using? Please provide specific versions.

C++ and googletest

What Bazel plugin version are you using?

CLion with Blaze 2025.05.27.0.1-api-version-251

Have you found anything relevant by searching the web?

This might be a CLion issue and not just a CLion with Blaze issue
https://youtrack.jetbrains.com/issue/CPP-41446/Debugger-has-stopped-hitting-breakpoints-again
https://intellij-support.jetbrains.com/hc/en-us/community/posts/21503159302418-CLion-won-t-debug-on-macOS-Sequoia-15-0

Any other information, logs, or outputs that you want to share?

No response

[mgalindo-sc]

So this indeed looks like a bazel issue, but I'm not sure its a plugin issue. When rebuilding, the intermediate files get cleaned up by bazel, but If you are rebuilding a previously cached artifact bazel will only produce the final output so LLDB won't find the object files for the test. E.g bazel-out/darwin_arm64-dbg/bin/src/foo/bar/_objs/test/Bar.o for test Bar will not be produced.
I'm closing since I don't think this is a plugin specific issue.