Open Bug 1375507 Opened 3 years ago Updated 2 years ago
Rust debug symbols are broken on mac
OS with rustc <1 .19 and codegen-units >1
https://github.com/rust-lang/rust/issues/39160 is the issue tracking the problem with codegen-units on macOS. It is fixed in rustc 1.19, and any version before that suffers from inscrutable failures when setting breakpoints in either lldb or gdb inside Rust code.
We could possibly detect this situation in http://searchfox.org/mozilla-central/diff/8f7b8a3663a48975af04a6ae9d8a972669bff63e/python/mozbuild/mozbuild/frontend/emitter.py#478 and emit a non-problematic value at all times.
(In reply to Josh Matthews [:jdm] from comment #1) > We could possibly detect this situation in > http://searchfox.org/mozilla-central/diff/ > 8f7b8a3663a48975af04a6ae9d8a972669bff63e/python/mozbuild/mozbuild/frontend/ > emitter.py#478 and emit a non-problematic value at all times. Unfortunately, that bit of code isn't emitting anything, it's verifying that the configuration for the gkrust libraries are what we expect them to be.
Ralph is bumping our Rust version to 1.19 in bug 1382743. That should fix this Rust debug symbol issue.
Depends on: 1382743
I spotted a build failure. Since :froydnj is talking about gkrust, I thought I would ask if this is the same bustage before filing a new bug.
You need to log in before you can comment on or make changes to this bug.