-
Notifications
You must be signed in to change notification settings - Fork 79
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
Fix unitialized access of err and erroneous error message. #41
base: main
Are you sure you want to change the base?
Conversation
I don't have a proper setup to test this yet for regressions, so I didn't build it. Again, I apologize if the changes are too pedantic. |
63af27a
to
bf4cca5
Compare
Hi! Thanks a lot for taking the interest in working on this. Your changes look good to me, just a couple of comments:
|
malloc(3) already sets errno and we should return on NULL. Signed-off-by: Christiano Haesbaert <[email protected]>
Saves you headache when stdout is not a tty. Signed-off-by: Christiano Haesbaert <[email protected]>
Preparation for a couple of fixes/improvements, these are only re-indents and some tabs vs spaces so that the next commit intention is clear. Signed-off-by: Christiano Haesbaert <[email protected]>
o Make sure we print errors and warnings to stderr. o Don't assume fork succeeds. o Use err(3) and warn(3), cuts some lines. o Keep braces for single liners as requested. Signed-off-by: Christiano Haesbaert <[email protected]>
Thanks for reviewing it. |
@haesbaert There seems to be some conflicts with this PR as a lot has been done since its submission. Do you mind rebasing on |
malloc(3) already sets errno and we should return on NULL.
Hi, sorry if this is too silly I was just going over the code and noticed it, also you could use err(3) or errx(3) and cut some lines.
I have more silly fixes like this I can push if you want.