The other way to do this would be to pass num_expected_locations = -1 when you
make the foo breakpoint, and then grab the breakpoint's number of locations and
assume you are going to hit the breakpoint that many times.
But changing the code so that the line you are breaking on is unambiguously o
This test actually almost succeeds on macOS. The problem is that your
breakpoint in the Foo constructor produces two line table entries so we hit the
foo breakpoint twice. If you change the test file to:
Index:
packages/Python/lldbsuite/test/functionalities/breakpoint/global_constructor/foo.c
