-
-
Notifications
You must be signed in to change notification settings - Fork 824
Stack overflow compiling serde_codegen 0.8 on OSX nightly #486
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
Comments
Hmm, I am using serde 0.8 with nightly and MIR on OS X for a while and have never run into this. |
@alexcrichton the serde-codegen build script parses the entire crate with quasi and then expands the quasi macros. Increasing the stack size would be easy (pack everything in a thread and set the RUST_MIN_STACK env var), but I have no way of testing it. I could simply pack everything in a thread and you can experiment with the RUST_MIN_STACK env var yourself. Once that works, I can add code that sets the RUST_MIN_STACK var to a value you have found to work (as long as it isn't already set). @alexbool I'm not sure whether Rust chooses the main thread's stack size depending on some system information, maybe it differs between your setup and @alexcrichton's. The difference might also be because of some compiler options. debug mode + no optimizations will obviously use more stack space than release mode + optimizations. |
Yeah unfortunately I've been unable to reproduce locally as well, it's only reproducing on Travis. It may be the case that rust-lang/rust#35409 fixes this, but in the meantime using |
Wait... It works without the changes or it should work with them? |
Oh it doesn't work yet, I was gonna wait for a merge so I can test out |
oh, good, that would have been weird. I published 0.8.1 which does all the syntex stuff in a thread, so hopefully |
Worked for me, thanks! |
Great |
I've been seeing some failures in compiling
serde_codegen
on Travis OSX builders using the nightly compiler:I wonder, is the build script for serde-codegen doing anything that might cause this? This started regressing for me about the time MIR codegen landed, and there's a few known stack-space issues with MIR, but for now could an explicitly large stack be used perhaps?
The text was updated successfully, but these errors were encountered: