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 up`unexpected panic` when compiling the `lalrpop` crate #32530
Comments
This comment has been minimized.
This comment has been minimized.
|
Perhaps fallout from #32293? |
This comment has been minimized.
This comment has been minimized.
afck
commented
Mar 28, 2016
|
The igd crate is also affected:
|
This was referenced Mar 28, 2016
This comment has been minimized.
This comment has been minimized.
|
This is also present in the |
This comment has been minimized.
This comment has been minimized.
|
triage: P-high |
rust-highfive
added
P-high
and removed
I-nominated
labels
Mar 31, 2016
pnkfelix
assigned
michaelwoerister
Mar 31, 2016
This comment has been minimized.
This comment has been minimized.
|
Might be fixed by #32579 once it lands. |
This comment has been minimized.
This comment has been minimized.
|
I've tested this locally against lalrpop, igd, and aurelius and #32579 indeed seems to do the trick. |
This comment has been minimized.
This comment has been minimized.
|
Not sure if this is relevant (especially since the issue seems to have been fixed), but just in case, I've noticed that |
This comment has been minimized.
This comment has been minimized.
|
@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. |
This comment has been minimized.
This comment has been minimized.
nightmared
commented
Apr 2, 2016
|
@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 |
This comment has been minimized.
This comment has been minimized.
|
Fixed by #32579 |
saghm commentedMar 27, 2016
When compiling the
lalrpopcrate 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.0oflalrpop, 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!