Actions
Bug #19578
closedabort() shows stack trace when run within rescue clause
Bug #19578:
abort() shows stack trace when run within rescue clause
Description
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.
Actions