rust/tests/ui/runtime/on-broken-pipe/auxiliary/assert-inherit-sig_dfl.rs

//@ aux-crate: sigpipe_utils=sigpipe-utils.rs
//@ compile-flags: -Zon-broken-pipe=inherit

fn main() {
    sigpipe_utils::assert_sigpipe_handler(sigpipe_utils::SignalHandler::Default);
}
Test `#[unix_sigpipe = "inherit"]` with both `SIG_DFL` and `SIG_IGN` Add a test that fails if `#[unix_sigpipe = "inherit"]` wrongly results in `SIGPIPE` being `SIG_DFL` if the parent has `SIG_IGN`. We have no current test for this particular case. 2024-04-01 11:27:48 +02:00			`//@ aux-crate: sigpipe_utils=sigpipe-utils.rs`
Change `SIGPIPE` ui from `#[unix_sigpipe = "..."]` to `-Zon-broken-pipe=...` In the stabilization attempt of `#[unix_sigpipe = "sig_dfl"]`, a concern was raised related to using a language attribute for the feature: Long term, we want `fn lang_start()` to be definable by any crate, not just libstd. Having a special language attribute in that case becomes awkward. So as a first step towards towards the next stabilization attempt, this PR changes the `#[unix_sigpipe = "..."]` attribute to a compiler flag `-Zon-broken-pipe=...` to remove that concern, since now the language is not "contaminated" by this feature. Another point was also raised, namely that the ui should not leak how it does things, but rather what the end effect is. The new flag uses the proposed naming. This is of course something that can be iterated on further before stabilization. 2024-04-28 18:02:21 +02:00			`//@ compile-flags: -Zon-broken-pipe=inherit`
Test `#[unix_sigpipe = "inherit"]` with both `SIG_DFL` and `SIG_IGN` Add a test that fails if `#[unix_sigpipe = "inherit"]` wrongly results in `SIGPIPE` being `SIG_DFL` if the parent has `SIG_IGN`. We have no current test for this particular case. 2024-04-01 11:27:48 +02:00
			`fn main() {`
			`sigpipe_utils::assert_sigpipe_handler(sigpipe_utils::SignalHandler::Default);`
			`}`