Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign uprustc 1.12.0 fails with SIGSEGV in release mode (syn crate 0.8.0) #36875
Comments
This comment has been minimized.
This comment has been minimized.
|
Steps for minimal repro:
|
bluss
added
the
regression-from-stable-to-stable
label
Oct 1, 2016
This comment has been minimized.
This comment has been minimized.
|
1.11 -> 1.12 regression since it used to work dtolnay/syn#20 (comment) |
This comment has been minimized.
This comment has been minimized.
Sorry, I'm confused. Ah, I guess you mean that this is fixed in the 1.13 beta? |
alexcrichton
added
I-nominated
T-compiler
labels
Oct 4, 2016
This comment has been minimized.
This comment has been minimized.
|
I can confirm that this works on the beta channel (1.13) but fails on the stable channel (1.12). I don't know what patch would need to be backported (maybe someone from @rust-lang/compiler recognizes the backtrace?), but I'm inclined to downgrade the priority here as a result. Thoughts? |
This comment has been minimized.
This comment has been minimized.
|
Can we get an assertion message of any kind? That could confirm it's a specific bug or another. |
This comment has been minimized.
This comment has been minimized.
|
@eddyb i.e., rebuild rust with LLVM assertions enabled? |
This comment has been minimized.
This comment has been minimized.
|
@nikomatsakis Using a nightly that's about as old as the release (i.e. 12 weeks ago) should work. |
This comment has been minimized.
This comment has been minimized.
|
@eddyb ah very good, will do UPDATE:
|
This comment has been minimized.
This comment has been minimized.
|
@nikomatsakis It could be one of the backports, in which case beta might work? Not sure if it has LLVM assertions enabled though (cc @alexcrichton). |
This comment has been minimized.
This comment has been minimized.
|
I believe betas don't have LLVM assertions enabled unfortunately |
This comment has been minimized.
This comment has been minimized.
|
I'll try a local beta build with asserts and see if i can bisect the patch that fixes. |
This comment has been minimized.
This comment has been minimized.
|
I have not been able to reproduce this with a local build of 1.12. |
brson
self-assigned this
Oct 6, 2016
brson
added
the
P-medium
label
Oct 6, 2016
nikomatsakis
removed
the
I-nominated
label
Oct 6, 2016
This comment has been minimized.
This comment has been minimized.
|
I'm worried that this failure is an artifact of our release build environment and am trying to reproduce it there. |
This comment has been minimized.
This comment has been minimized.
|
I've reproduced this inside the docker image we used for the 1.12 release:
This image has since had a significant upgrade. I have no idea what thing changed to make the problem go away. This does suggest a risk of doing a 1.12 point release: our build environment has changed significantly. I'm going to leave this open until we've thought about a 1.12 point release, but I think there's nothing left to do here. |
svend commentedSep 30, 2016
•
edited
To reproduce:
I expect this to compile, instead it fails with:
Running the rustc command by hand results in a core dump:
rustc version:
I cannot reproduce this failure with 1.11.0.
In the rustc irc channel, it was noted that this fixed in beta already, and that the following backtrace (from https://gist.github.com/nagisa/682b493e40729c1f322966f8c21e00c6) would be relevant: