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?
to your account
I have looked at a few source files for your current software. I have noticed that some checks for return codes are missing.
Would you like to add more error handling for return values from functions like the following?
The text was updated successfully, but these errors were encountered:
metalink: add some error checks
malloc() and strdup() calls without checking return codes.
Reported-by: Markus Elfring
vms_realwfilesize() doesn't have any fseek calls. I assume you mean the ones in operate_do(). I consider them mostly harmless. The same goes for the parse_cert_parameter strdups.
The metalink function was improved slightly in commit 3ac3331.
Sorry, something went wrong.
I suggest to avoid ignorance of return values a bit more.
Are you interested to apply aspect-oriented software development?
How do you think about to encapsulate error detection and corresponding exception handling as a reusable aspect in your software?
Can you identify any actual problems or bugs due to your discoveries? Can you submit a patch with your suggested fixes?
How do you think about to improve static source code analysis also for your software?
Do you find information sources like the following useful?
Does that mean you can't identify a problem or provide a patch?
No, he wants to have a long-winded argument about software architecture!
The suggested tools can help to transform source code in various ways.
Which transformations are acceptable for you to be performed by another software tool automatically?
No bug then. Closed.
No branches or pull requests