This is a wild #rust toolchain bug:

[wtfismyip@gnu.gl]

This is a wild #rust toolchain bug:

Can only repro when the call to gettid is in a library crate, and only when it has a certain name, and only when not using -C target-feature=-crt-static, only when using LTO... The boundary is exactly at std! Crate names alphabetically ≥ std fail (including std itself), and crate names < std work!

Calling libc gettid segfaults on x86_64-unknown-linux-musl · Issue #154439 · rust-lang/rust

View all comments This is a very strange one. Since 289fe36 (I bisected; cc @tgross35), my program that calls libc's gettid segfaults when built for x86_64-unknown-linux-musl. However, I can only reproduce this when the call to gettid is...

GitHub (github.com)