Skip to content
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

wio causes LLVM to explode violently #4

Open
DanielKeep opened this issue Feb 14, 2016 · 2 comments
Open

wio causes LLVM to explode violently #4

DanielKeep opened this issue Feb 14, 2016 · 2 comments

Comments

@DanielKeep
Copy link

Firstly, this is based on commit 5a80521 because the current HEAD doesn't typecheck on 64-bit.

Checking out and building wio with cargo build --release --target x86_64-pc-windows-msvc with the latest version of the VC++ Build Tools and rustc 1.8.0-nightly (ce4b75f25 2016-02-12) (latest nightly as of 2016-02-13), produces:

[master] > cargo build --release --target x86_64-pc-windows-msvc
   Compiling wio v0.1.1 (file:///F:/Scratch/repos/wio-rs)
Assertion failed!

Program: C:\Users\drk\AppData\Local\.multirust\toolchains\nightly\bin\rustc.exe File: C:/bot/slave/nightly-dist-rustc-win-gnu-32/build/src/llvm/include/llvm/ADT/DenseMap.h, Line 1025

Expression: isHandleInSync() && "invalid iterator access!"

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Could not compile `wio`.

To learn more, run the command again with --verbose.

Followed by a "rustc.exe has stopped working" dialog with the following:

Problem signature:
Problem Event Name: APPCRASH
Application Name: rustc.exe
Application Version: 0.0.0.0
Application Timestamp: 38666230
Fault Module Name: rustc_llvm-fd663c41.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 6c756465
Exception Code: 40000015
Exception Offset: 014057d8
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 3081
Additional Information 1: 8d13
Additional Information 2: 8d133e790ce9876f6238c6d446efdb4e
Additional Information 3: e1a4
Additional Information 4: e1a4fcae1a4e1dbed8f1806581b8db85

I do not get this crash on non-release, nor do I get it for i686-pc-windows-gnu (debug or release).

@retep998
Copy link
Owner

A good thing to point out here is that you used i686-pc-windows-gnu for the host and x86_64-pc-windows-msvc for the target so it is a cross compile.

@DanielKeep
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants