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
execv error codes #1590
Comments
@petermax2 is this finished? It seems like you worked on this but the boxes are not ticked yet. |
Not yet, because I wasn't aware of it (not assigned). But I can have a look! |
Yes, I assigned you just now because in some commits you already mentioned the issue.
Thank you so much! |
Just to be clear, do you have something like this in mind?
Write the error description to the stderr pipe:
Receive the error description from the pipe.
|
From the man page: "On success, execve() does not return, on error -1 is returned, and errno is set appropriately.". So actually, whenever it returns, it was an error which should be reported.
In PRs it is much easier to discuss code. Can you please create a PR? |
… gpg module See ElektraInitiative#1590 and ElektraInitiative#3137 for full discussion.
I fixed |
Thank you! |
I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue. |
I closed this issue now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue. |
Seems like we checked the error codes of execv wrong in 3 out of 4 places:
We should either communicate failed execv by the exit status (as done in src/tools/kdb/external.cpp:196) or by pipes (then we could communicate the errno or even strings).
@tom-wa Can you fix the shell plugin please?
@petermax2 Can you fix the crypto plugin please?
The text was updated successfully, but these errors were encountered: