-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Assertion failing in constructAbstractSubprogramScopeDIE if compiled with -g #14930
Comments
This reverts commit 6f135b0.
Stack trace:
|
Thanks for the report! I'll see if I can reproduce it. |
I've rebuilt my local rustc with following:
and strangely enough the problem seems to be fixed for both local & nightly installs (well, I suppose nightly actually uses libs from local 😄 ) |
That's possible, I don't know the intricacies of the build system too well |
For now it's known broken on a clean host install of rust-nightly. Can you please reopen? I'll confirm if that will happen with next nightly build. |
Woops, thanks @huonw. |
A bit more details, now that I have rustc failing in debug configuration. In
FWIW, this is the definition of /// Returns task stack pointer (PSP).
#[cfg(not(test))]
#[inline(always)]
pub fn get_task_stack_pointer() -> u32 {
let mut val: u32;
unsafe { asm!("mrs $0, psp" : "=r"(val)) };
val
} |
This might also be of interest (it points to here).
|
@farcaller Thanks a lot for the detailed information. |
Just a quick followup: I tried to reproduce this in a single file, so far with no success. If you wonder, the code is being compiled with the following flags:
|
@farcaller it's been a while, is this still failing for you? |
Haven't seen it in a while. |
Okay, then I'm going to give it a close. If we see it pop up again, let me know! |
It's broken again. |
* Without LTO, the executable will crash under VirtualBox. I'm not sure why but I'm not going to bother figuring that out. * LTO and debugging symbols don't mix, so disable the latter for now. See <rust-lang/rust#14930>.
… r=Veykril fix: let glob imports override other globs' visibility Follow up to rust-lang#14930 Fixes rust-lang#11858 Fixes rust-lang#14902 Fixes rust-lang#17704 I haven't reworked the code here at all - I don't feel confident in the codebase to do so - just rebased it onto the current main branch and fixed conflicts. I'm not _entirely_ sure I understand the structure of the `check` function in `crates/hir-def/src/nameres` tests. I think the change to the test expectation from rust-lang#14930 is correct, marking the `crate::reexport::inner` imports with `i`, and I understand it to mean there's a specific token in the import that we can match it to (in this case, `Trait`, `function` and `makro` of `pub use crate::defs::{Trait, function, makro};` respectively), but I had some trouble understanding the meaning of the different parts of `PerNs` to be sure. Does this make sense? I tested building and using RA locally with `cargo xtask install` and after this change the documentation for `arrow_array::ArrowPrimitiveType` seems to be picked up correctly!
What interesting is that it fails with rust nightly but works ok with my local rust configuration:
Update: those timestamps look to same, that's probably not a coincidence :-) anyways, my local rustc is surely built from 6d8342f.
My rust was configured as
The text was updated successfully, but these errors were encountered: