kendalharland wrote: > The only way that this could succeed on the breakpoint but fail on the > location is that there is more than one location and the one the test is > setting it on (the zeroth) is not the one that's hit. Since this test is > "does a breakpoint condition on a location work" not "does this breakpoint > always only produce one location" it might be better to just put the > breakpoint on all the locations, and see if the one that is hit does work.
Thanks for the context! In this PR I learned that the set of compilers I was using to build LLVM are different from the existing lldb-aarch64-windows builder. After fixing that, I am no longer seeing this test fail. I've removed the top commit and left only the one that splits the test assertion to produce a more clear failure message. https://github.com/llvm/llvm-project/pull/100487 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
