-
Notifications
You must be signed in to change notification settings - Fork 13.3k
segfault with small Rust program #10325
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
Comments
The infinite recursion is a known bug occurring from infinitely sized types #3779, but a stack overflow should not occur. |
Hi @chetmurthy - nice to run into you here (we met at the Berkeley OSQ retreat 10 years ago). The fix is to change @thestinger - #3779 says there's a stack overflow, and it hasn't been closed, so I'm going to treat this as a duplicate. |
I get the |
I agree that this is a dupe of #3779, the runtime is doing what it should be doing, which is printing that a stack overflow was detected and then aborting. |
@alexcrichton: By something is broken about the stack checks I mean that while it works locally on Linux x86_64, it's not working for the reporter of this bug. |
Crap. I should have mentioned my platform. Linux x86 -- 32bit -- Ubuntu 13.04. |
I don't believe that we had stack checks in 0.8, I think they're an 0.9-pre thing |
Ah I missed the fact that an error message was printed for them with the git commit. Ignore me! :) |
cast_possible_truncation: issue proper help message Fixes rust-lang#10325 --- changelog: Sugg: [`cast_possible_truncation`]: Corrected the lint name in help message [rust-lang#10330](rust-lang/rust-clippy#10330) <!-- changelog_checked-->
I've got a small Rust program, trying to implement a binary search tree. With Rust 0.8, the compiler segfaults. WIth GIT revision 8ea2123, I get a nicer error-message, THEN a segfault. Looks like some sort of infinite stack-recursion.
I'm including the program.
The text was updated successfully, but these errors were encountered: