-
Notifications
You must be signed in to change notification settings - Fork 30
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
SIGSEGV when compiling on latest nightly #25
Comments
Looks like things work when I add
|
Hmm... I cannot appear to reproduce this when I attempt to compile the program with the provided Dockerfile. Perhaps there's an issue with the linker being selected locally. I'll do some more research. |
Err, scratch that. It also appears to be an issue with Dockerfile.ci:
So it appears this is not just localized to my system, and it does appear to be related to an issue with the nightlies. |
I had a similar error |
Also had the same issue in my setup, this also seems to fix it 👍 |
I had the same issue and got it working with the
I got the output size down from ~700K to 8K which is acceptable to me for now. |
I have the same problem. With or without erdezt's changes to [profile.dev]:
|
@erdeszt's profile works reliably. Without it, I get the following logs:
|
Slight modification of @erdeszt's workaround because I really just couldn't do without that release build (Cargo.toml in my case):
I've tested this modification on the dockerfile provided, it works on that and will also build for release. |
Before this, 'cargo build -Z build-std=core --target avr-atmega328p.json' would fail with linking errors to 'abort' and 'memcpy' symbols. After this patch, a debug mode executable can be successfully generated again.
Waits for seems to be fixed, I can't reprocuce the |
rust-lang/rust#76930 being solved allowed me to close this is issue. |
This issue has reported upstream at rust-lang/rust#76930. Following the AVR Rust book, the program cannot compile due to a segmentation fault when compiling the
core
crate on the latest nightly build.Using the debug target also fails with more information:
The text was updated successfully, but these errors were encountered: