Fix this test so that the breakpoints you set are

unambiguously on one bit of code.  On macOS these
lines mapped to two distinct locations, and that
was artificially throwing off the test.

llvm-svn: 319472

diff --git a/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/global_constructor/foo.cpp b/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/global_constructor/foo.cpp
index 76950f2..f959a29 100644 (file)
--- a/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/global_constructor/foo.cpp
+++ b/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/global_constructor/foo.cpp
@@ -1,5 +1,7 @@
 #include "foo.h"
 
-Foo::Foo() : x(42) {} // !BR_foo
+Foo::Foo() : x(42) {
+    bool some_code = x == 42;  // !BR_foo
+} 
 
 Foo FooObj;

diff --git a/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/global_constructor/main.cpp b/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/global_constructor/main.cpp
index b0e39c1..d1c8038 100644 (file)
--- a/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/global_constructor/main.cpp
+++ b/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/global_constructor/main.cpp
@@ -5,7 +5,9 @@ struct Main {
   int x;
 };
 
-Main::Main() : x(47) {} // !BR_main
+Main::Main() : x(47) {
+    bool some_code = x == 47; // !BR_main
+}
 
 Main MainObj;