-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
unexpected panic
when compiling the lalrpop
crate
#32530
Comments
Perhaps fallout from #32293? |
The igd crate is also affected:
|
This is also present in the |
triage: P-high |
Might be fixed by #32579 once it lands. |
I've tested this locally against lalrpop, igd, and aurelius and #32579 indeed seems to do the trick. |
Not sure if this is relevant (especially since the issue seems to have been fixed), but just in case, I've noticed that |
@michaelwoerister @saghm Makes sense. The problem occurs when the same crate is used in two different versions. This resulted in two distinct types which would get the same mangled names for their drop functions, resulting in a name conflict. |
@dotdash You're probably right. I'm currently working on a little project which uses at the same time nickel (a http server based on hyper) and hyper itself, and it generates the following stacktrace:
(This happens on However, I can confirm that it works flawlessly with |
Fixed by #32579 |
When compiling the
lalrpop
crate as a dependency for my project, I got an error message saying that the compiler panicked. As per the error message, I'm submitting a bug report.I'm not sure exactly what code caused the compiler to panic unfortunately, as the error occurred when cargo was compiling a dependency.
The crate is version
0.11.0
oflalrpop
, and the compiler version is the latest nightly (rustc 1.9.0-nightly (d5a91e6 2016-03-26).The exact error message (including a backtrace) is the following:
In the event that this isn't actually a compiler bug, sorry about the hassle. If it is, let me know if there's anything else I can do to help!
The text was updated successfully, but these errors were encountered: