-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CARGO_INCREMENTAL breaks debuginfo #3905
Comments
cc @michaelwoerister and @nikomatsakis |
Is this on OSX? If so this might be the same problem as rust-lang/rust#39160. |
Yes, this on macOS
Jonathan
…_____________________________
From: Michael Woerister <notifications@github.com<mailto:notifications@github.com>>
Sent: Friday, April 7, 2017 9:00 PM
Subject: Re: [rust-lang/cargo] CARGO_INCREMENTAL breaks debuginfo (#3905)
To: rust-lang/cargo <cargo@noreply.github.com<mailto:cargo@noreply.github.com>>
Cc: Jonathan Turner <jturner@mozilla.com<mailto:jturner@mozilla.com>>, Author <author@noreply.github.com<mailto:author@noreply.github.com>>
Is this on OSX? If so this might be the same problem as rust-lang/rust#39160<rust-lang/rust#39160>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#3905 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAhZVqf55Y3OJzTbuhLNht9UqH-VfWPIks5rtfs8gaJpZM4M2buK>.
|
@jonathandturner care to try and narrow it down by building w/o incremental, but w/ codegen-units? |
eg, by setting |
@nikomatsakis - yes, I can confirm the -Ccodegen-units=256 causes the same issue. |
Closing as a dupe of rust-lang/rust#39160 (plz fix kthx 😄) |
In the same project, if I compile with CARGO_INCREMENTAL=1 and run the application through lldb, I get:
Same project without:
The latter, I believe, is what we want as it's what you'd get by hand when using
rustc
. With incremental turned on, we can't easily step into the original source. Instead, we end up stepping through the assembly.The text was updated successfully, but these errors were encountered: