Skip to content

SIGILL (possibly OOM) on 32-bit linux build machine #18777

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.

Sign up for GitHub

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

Jump to bottom
Closed
bkoropoff opened this issue Nov 8, 2014 · 3 comments
Closed

SIGILL (possibly OOM) on 32-bit linux build machine #18777

bkoropoff opened this issue Nov 8, 2014 · 3 comments

Comments

@bkoropoff
Copy link
Contributor

Logs: http://buildbot.rust-lang.org/builders/auto-linux-32-nopt-t/builds/2161/steps/test/logs/stdio

Occurred on PR #18730, which was too trivial a change to have been the cause
@bkoropoff
Copy link
Contributor Author

#18483 also had a similar problem on the same machine.

Logs: http://buildbot.rust-lang.org/builders/auto-linux-32-nopt-c/builds/2141/steps/compile/logs/stdio

@bkoropoff bkoropoff changed the title Core (possibly OOM) on 32-bit linux build machine SIGILL (possibly OOM) on 32-bit linux build machine Nov 8, 2014
@eddyb
Copy link
Member

eddyb commented Nov 8, 2014

#18483 didn't change codegen, but I was worried it was responsible somehow.

I didn't realize the abort could have been OOM, but that makes sense in retrospective.
This calls for a quick resolution of #18678.

@alexcrichton alexcrichton mentioned this issue Nov 8, 2014
Merged
@thestinger
Copy link
Contributor

Closing in favour of #18784.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@eddyb @thestinger @bkoropoff