Out-of-memory causes SIGILL

[mpdn]

This snippet: (Playpen link)

#![allow(unstable)]

extern crate test;

fn main() {
    let a: Vec<u8> = Vec::with_capacity(::std::usize::MAX);
    ::test::black_box(a);
}

Causes the program to close with a SIGILL (Illegal instruction) error. I would have expected something like a SIGSEGV instead.

[sfackler]

This is working as intended. Rust calls the LLVM trap intrinsic which is compiled to the ud2 instruction which in turn generates a SIGILL..

[mpdn]

But oom calls abort. Shouldn't it use SIGABRT instead? To me, SIGILL makes it seem like the compiler is at fault, which it clearly isn't.

[kmcallister]

This does confuse people. We could override LLVM's choice if we want to. A standard SIGABRT handler might be nice.

[alexcrichton]

Closing as a dupe of #14674, but thanks for the issue!

[BenWiederhake]

How is this a duplicate? The other issue is about OOM not being printed on stackoverflow, which seems to be fixed.
OOM still causes SIGILL, which is very confusing indeed, and should be fixed somehow. So I'd say this is still an "open" issue.

Maybe oom_handler (which for my system resides in src/libstd/sys/unix/mod.rs) should also call to ::libc::abort() instead of ::intrinsics::abort, just like in the fix for #31273?

As Ixrec helpfully pointed out in chat, I probably should have linked to the pull request by number: #31457

[sfackler]

The word "stack" does not appear in #14674, unless I'm missing somethign.