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

Check return codes everywhere #46

Open
elfring opened this issue Mar 26, 2016 · 3 comments
Open

Check return codes everywhere #46

elfring opened this issue Mar 26, 2016 · 3 comments

Comments

@elfring
Copy link

elfring commented Mar 26, 2016

Would you like to add more error handling for return values from functions like the following?

@achadwick
Copy link
Member

Sounds reasonable. Those functions should probably return NULL if the functions you've identified fail.

Do you have a patch, and/or can you further define the scope for this? "Everywhere" is too broad to work from.

@elfring
Copy link
Author

elfring commented Mar 27, 2016

I suggest to avoid ignorance of return values a bit more.
How do you think about to improve static source code analysis also for this software?

@achadwick
Copy link
Member

We generally like to automate tests in response to github commits. Perhaps point coverity at it?
https://scan.coverity.com/travis_ci

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

No branches or pull requests

2 participants