You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To apply our LLDB settings, we set a custom bazel.lldbinit file in every generated scheme. Unfortunately, for some reason Apple Watch schemes don't support this property.
Reproduction steps
This should be reproducible in an empty project with a watchOS target in BwB. As you can see, there's no "LLDB Init File" field. I checked Xcode 14 and also that this doesn't seem to be supported.
After moving the contents of my generated bazel.lldbinit to ~/.lldbinit, breakpoints started working just fine.
Expected behavior
LLDB settings should be applied correctly in order for debugging to work.
Versions
Bazel: 5.3.1
rules_xcodeproj: 0.9.0
Additional context
Internally in our existing non-Bazel generated project, we work around this by modifying the user ~/.lldbinit directly. This is not ideal and breaks in some cases (for example when changing project or when using multiple copies of the same project), so we should find a way to address this.
The text was updated successfully, but these errors were encountered:
Fixes#1237. Fixes#1523.
There are some schemes that don't respect the custom lldbinit, such as
watchOS apps and app extensions. To accommodate all targets equally, we
now modify `~/.lldbinit` to load a `~/.lldbinit-rules_xcodeproj`. We can
revert this change if Xcode fixes its scheme creation 🙂.
Describe the bug
To apply our LLDB settings, we set a custom
bazel.lldbinit
file in every generated scheme. Unfortunately, for some reason Apple Watch schemes don't support this property.Reproduction steps
This should be reproducible in an empty project with a watchOS target in BwB. As you can see, there's no "LLDB Init File" field. I checked Xcode 14 and also that this doesn't seem to be supported.
After moving the contents of my generated
bazel.lldbinit
to~/.lldbinit
, breakpoints started working just fine.Expected behavior
LLDB settings should be applied correctly in order for debugging to work.
Versions
Additional context
Internally in our existing non-Bazel generated project, we work around this by modifying the user
~/.lldbinit
directly. This is not ideal and breaks in some cases (for example when changing project or when using multiple copies of the same project), so we should find a way to address this.The text was updated successfully, but these errors were encountered: