Skip to content
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

CommandResult's lazy vals get null value when remote command throwing a "SEGV" as exitSignal #32

Open
thomassun opened this issue Nov 4, 2015 · 0 comments

Comments

@thomassun
Copy link

the lazy vals(exitCode,exitErrorMessage, i/o streams etc.) gives null instead of Option for the channel as result of a remote command causes "Segmentation fault" or "Floating point exception" where the exception stored in exitSignal
it's easy to reproduce, just compile following c code and run it's binary with exec and then access the exitCode, it throws java.lang.NullPointerException

int main(int argc, char *argv[]){
int x;
x = 100/0;
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant