scopeguard | Rust crate for a convenient RAII scope guard

Given the constraints, I'd go with the obvious solution, a RefCell. It has a bad rap of being overused, but is actually designed for scenarios like this one. Using RefCell without an Rc is a good sign of doing it right.

RefCell allows the guard to capture the value by shared reference, which leaves it available for your use:

This behavior is intended.

From a comment by Jonas Schievink in Why does panicking in a Drop impl cause SIGILL?:

It calls intrinsics::abort(), which LLVM turns into a ub2 instruction, which is illegal, thus SIGILL

I couldn't find any documentation for how double panics are handled, but a paragraph for std::intrinsics::abort() lines up with this behavior:

The current implementation of intrinsics::abort is to invoke an invalid instruction, on most platforms. On Unix, the process will probably terminate with a signal like SIGABRT, SIGILL, SIGTRAP, SIGSEGV or SIGBUS. The precise behaviour is not guaranteed and not stable.

Curiously, this behavior is different from calling std::process::abort(), which always terminates with SIGABRT.

The illegal instruction of choice on x86 is UD2 (I think a typo in the comment above) a.k.a. an undefined instruction which is paradoxically reserved and documented to not be an instruction. So there is no corruption or invalid jump, just a quick and loud way to tell the OS that something has gone very wrong.

Seems like a bug, already reported and fixed for gcc: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66139

I suppose, std::shared_ptr<> is partially created during exception throw

As a workaround, you could prevent copy elision:

Reqwest lists OpenSSL as a requirement on Linux due to it using native-tls, which depends on openssl. You need to install the pkg-config and libssl-dev packages:

The problem is quite clear:

Your Rust target architecture (64-bit) does not match your python interpreter (32-bit)

Either upgrade your Python interpreter to 64 bit, or use rustup to install a 32 bit Rust target

Edit: Here is how you could manually target 32 bit on a x86_64 machine