[ruby-core:113128] [Ruby master Bug#19578] abort() shows stack trace when run within rescue clause
From:
"Dan0042 (Daniel DeLorme) via ruby-core" <ruby-core@...>
Date:
2023-04-05 13:28:27 UTC
List:
ruby-core #113128
Issue #19578 has been updated by Dan0042 (Daniel DeLorme). jeremyevans0 (Jeremy Evans) wrote in #note-3: > I agree. Can you please submit a pull request for it? Done: https://github.com/ruby/ruby/pull/7664 ---------------------------------------- Bug #19578: abort() shows stack trace when run within rescue clause https://bugs.ruby-lang.org/issues/19578#change-102663 * Author: Dan0042 (Daniel DeLorme) * Status: Rejected * Priority: Normal * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- I sometimes use the pattern `print(str) rescue abort` in order to exit without stack trace when the output of a ruby program is interrupted by SIGPIPE, ex: `./printstuff.rb | head` It seems that since ruby 2.7 this results in printing the stack trace. This is not the case when using `abort` by itself. Is this intended? I would expect `abort` to behave much like `exit(1)`, as it always has. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- [email protected] To unsubscribe send an email to [email protected] ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/