Skip to content
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

Unknown Compiler Error #3813

Closed
kyledj opened this issue Oct 19, 2012 · 1 comment
Closed

Unknown Compiler Error #3813

kyledj opened this issue Oct 19, 2012 · 1 comment

Comments

@kyledj
Copy link

kyledj commented Oct 19, 2012

Receive a very cryptic compiler error with the following code

use core::option::Option;

enum Something {
    Value(~str),
    Other(int)
}

struct Record {
    num: int,                
    start: Option<RecordValue>
}

struct RecordValue {
    value: Something,
    next: Option<RecordValue>
}

fn main() {
}

The output:

rust: task 7f8fe2600fc0 ran out of stack
error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug
note: try running with RUST_LOG=rustc=0,::rt::backtrace to get further details and report the results to github.com/mozilla/rust/issues
rust: task failed at 'explicit failure', /Users/kylejones/src/rust/rust/src/rustc/driver/rustc.rs:241
rust: domain main @0x7f8fe3000010 root task failed
rust: task failed at 'killed', /Users/kylejones/src/rust/rust/src/libcore/task.rs:667
@catamorphism
Copy link
Contributor

You need to change the type of the start and next fields to Option<@RecordValue>. The compiler should be giving you a nicer error message here, but there's already a bug open on it: #3779 .

Thanks for the report!

bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
RalfJung pushed a commit to RalfJung/rust that referenced this issue Aug 18, 2024
Testcase fix for epoll

Fixes rust-lang#3811

This PR:
- Fixed the error in ``epoll_ctl_del`` test
- Simplified the logic in ``epoll_ctl_mod`` test
- Added a new test to check if flag that we don't register won't trigger notification (double negation sounds a bit confusing here, feel free to suggest a better one ;) )
- Use assert_eq(0) for epoll_ctl test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants