-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Segfault moving out of a struct and then calling a move-out-of-self method #4759
Labels
A-lifetimes
Area: Lifetimes / regions
E-needs-test
Call for participation: An issue has been fixed and does not reproduce, but no test has been added.
I-crash
Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
Comments
ghost
assigned nikomatsakis
Feb 2, 2013
The second issue can be reproduced with much more minimal code:
This is actually not related to the struct/tuple destructuring but a trait impl of primitive types. |
Not critical for 0.6; removing milestone. |
Reproduced with 64963d6. Nominating for milestone 5, production-ready |
Seems to be fixed in master |
graydon
added a commit
to graydon/rust
that referenced
this issue
Aug 2, 2013
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Aug 14, 2013
Closes rust-lang#3907 Closes rust-lang#5493 Closes rust-lang#4464 Closes rust-lang#4759 Closes rust-lang#5666 Closes rust-lang#5884 Closes rust-lang#5926 Closes rust-lang#6318 Closes rust-lang#6557 Closes rust-lang#6898 Closes rust-lang#6919 Closes rust-lang#7222
It looks like a test for this was added already. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-lifetimes
Area: Lifetimes / regions
E-needs-test
Call for participation: An issue has been fixed and does not reproduce, but no test has been added.
I-crash
Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
This code segfaults:
with this output:
and this stack trace:
When getting rid of the unique pointer, I instead get an llvm assertion. Here's the code:
and the output:
and this stack trace:
The text was updated successfully, but these errors were encountered: