You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was able to reproduce the crash locally on windows.
Building foundationdb-sys alone doesn't crash, but while building foundationdb-sys for foundationdb it does.
Well, I guess, this is expected behavior of panic on windows.
To give a bit of context, I want to build this code with code coverage, and due to the removal of -Zno-landings-pads I was migrating to use -Cpanic=abort.
I don't know how I should resolve this problem, proc_macro2 use catch_unwind and this embeded quite deep inside the bindgen crate.
Is there a way to execute build script without -Cpanic=abort while still building the crate with -Cpanic=abort ?
Speedy37
changed the title
-Cpanic=abort cause STATUS_ILLEGAL_INSTRUCTION (ud2) in build script-Cpanic=abort IllegalInstruction (ud2) in build script
May 26, 2020
Speedy37
changed the title
-Cpanic=abort IllegalInstruction (ud2) in build script-Cpanic=abort IllegalInstruction in build script
May 26, 2020
I tried this code:
On this repository: https://github.com/Clikengo/foundationdb-rs
I expected to see this happen: A correct build or a correct abort call
Instead, this happened: the processor reach an illegal instruction.
https://github.com/Clikengo/foundationdb-rs/runs/709083830
I was able to reproduce the crash locally on windows.
Building foundationdb-sys alone doesn't crash, but while building foundationdb-sys for foundationdb it does.
Meta
rustc --version --verbose
:Backtrace
The text was updated successfully, but these errors were encountered: