Open RussTedrake opened 8 months ago
Most likely, these two lines are the proximate cause of the error message:
Those two settings are (in modern times) particularly problematic. I guess they were less problematic 5 years ago. I think for them to work correctly, you need to do the "apple debug" in a completely fresh checkout, not re-use an existing build. (Or equivalently, bazel clean --expunge
first.)
Long term, my goal would be to not have --config=apple_debug
at all. The question would be if we just do --compilation_mode=dbg
(aka -c dbg
) on its own (which is the same as we do on Ubuntu), does lldb debugging still work?
Unfortunately all of the TRI macs are out of service at the moment, so I can't investigate more.
There are some google hits on debugging with dSYM and bazel. If the plain -c dbg
doesn't get us what we need, maybe there are some internet tips that would get it working.
Per #21936, macOS Debug is no longer covered by CI. It's possible that we should likewise disclaim support for any special Bazel setup to try to make it easier, since we can't automatically test it.
What happened?
fails with
throws those errors and also a bunch from conex
cc @frankpermenter
Version
master
What operating system are you using?
macOS 14 (Sonoma)
What installation option are you using?
compiled from source code using Bazel
Relevant log output