stack overflow. Caused by: Could not compile curve25519-dalek

[SemElVik]

#252 (comment)

[hdevalence]

Can you post any information about how to reproduce this problem?

[SemElVik]

I did not quite understand your question, what do you mean by the word "reproduce"?
how can you get this error?
...
This error occurred not only with me.
there is another person with the same problem.

This assembly happens every other time. 5 times not well -1 times good.
conditionally so.
From the root, it did not work out at all.

[hdevalence]

Yes, I mean what steps you do to get this error.

Does it happen every time you do those steps, or only sometimes?

How can I test the error?

[SemElVik]

3 builds are working at the moment and I can not recompile them.
there is another person with the same error. I will clarify with him.
if nothing happens, I will try to get this error myself personally.., and then I will give a reproduction

[gaia]

unconfirmed, but I was only able to reproduce the issue (in building tmkms) when I installed rust via apt install cargo. when I used curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh tmkms compiled fine.

[tarcieri]

@gaia interesting. I'll note that I build tmkms using Rust as installed from RPMs, and have never experienced this issue.

Perhaps the Debian/Ubuntu packages are doing something odd.

[hdevalence]

@gaia What are the respective versions of rust installed by each method?

[gaia]

@hdevalence
via cargo: rustc 1.32.0
via sh.rustup.rs: rustc 1.36.0

[warner]

I just spun up a couple of VMs with various debian/ubuntu versions, and cargo build --release worked each time:

• ubuntu/bionic (rustc-1.35.0)
• ubuntu/cosmic (rustc-1.34.1)
• ubuntu/disco (rustc-1.35.something)
• ubuntu/eoan (rustc-1.35.something)
• debian/buster (rustc-1.34.2)

I didn't encounter a distribution which includes rustc-1.32.0.

@gaia what version of the OS are you using? And what architecture (amd64)?

FWIW, rustup run 1.32.0 cargo test worked for me, on debian/stretch, with the toolchain from sh.rustup.rs. So it seems like more than just the rustc version.

[gaia]

@warner Ubuntu 18.04.2 amd64

[warner]

Hm, on a fresh ubuntu-18.04.2 system ("bionic") I'm getting rust 1.35.0, but that's including some updates repo.

@gaia what do dpkg -s cargo |grep Version and dpkg -s rustc |grep Version report?

[SemElVik]

ok.
cos@cos:~$ dpkg -s rustc |grep Version Version: 1.32.0+dfsg1+llvm-1ubuntu1~18.04.1
cos@cos:~$ dpkg -s cargo |grep Version Version: 0.33.0-1ubuntu1~18.04.1

perhaps on that moment compilation there was no version 1.35 yet.
not sure when it refreshed

[warner]

for reference, http://security.ubuntu.com/ubuntu/pool/universe/r/rustc/ has the older .deb packages, including the 1.32.0+dfsg1+llvm-1... version that seems to be on your machine. It appears to be non-trivial to downgrade an updated bionic system to use that version, though, at least when I tried to dpkg install that one package, I got errors about libstd-rust-dev and libc too.

[gaia]

dpkg -s cargo |grep Version

I already have the updated cargo and rustc on my machine now. at that time it was as mentioned in #261 (comment)

[warner]

I've got users who hit this problem too.. if they can reproduce it, what information would you want from them? Or should I just recommend they upgrade to rustc > 1.32.0?

[hdevalence]

I'm not sure what the problem is, so I'm not sure what information would be the most useful. I think that compilation should not trigger a stack overflow. Since it apparently does, in some cases, there's a question of what the cause is: either a) in some part of rustc or b) in the build.rs script, which are the two places that execute code during compilation. In case a) I guess there's nothing to do but to update rustc; in case b) I think the cleanest solution is #217 which hopefully removes the problem entirely?