New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proc.exitcode is zero for processes killed by signals #5512
Comments
From slaven@rezic.deIf an external command called by run dies with an signal, then there's no exception: $ perl6 -e 'run "perl", "-e", q{kill SEGV => $$}; say "should not happen"' I would expect something similar to: $ perl6 -e 'run "perl", "-e", q{exit 1}; say "should not happen"' except that the explanation should say something like (signal: SEGV) or (signal: segmentation fault), maybe with core dump information appended. Version info: Operating system: Debian/jessie |
From @zoffixznetOn Mon Aug 01 13:52:57 2016, slaven@rezic.de wrote:
To clarify a bit: `run` doesn't throw exceptions. It returns a Proc object, which throws when it's sunk if the exit code is non-zero. In this case, the issue is the killed processes have 0 as their exit code: $ perl6 -e 'run("perl", "-e", q{kill SEGV => $$}).exitcode.say' |
The RT System itself - Status changed from 'new' to 'open' |
This was fixed in (2019-09-05) rakudo/rakudo@225b1c5, a dup ticket is here: rakudo/rakudo#3149 |
Migrated from rt.perl.org#128805 (status was 'open')
Searchable as RT128805$
The text was updated successfully, but these errors were encountered: