Completion of error handling

[elfring]

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

• malloc ⇒ tokinit
• printf ⇒ bsdump
• strdup ⇒ setns

[oridb]

Checking errors on printf is pretty useless. Otherwise, I'll gladly take a patch for this

[elfring]

I suggest to avoid ignorance of return values a bit more. Would you like to detect every error situation as early as possible?

[refi64]

What are you going to do if printf fails though? It's not like you can log a message. There's no point in checking IMO.

[elfring]

• Do you care also for file output failures?
• How do you think about to determine a corresponding program exit status?

[oridb]

As stated, pull requests welcome.

[elfring]

• How do you think about to improve static source code analysis also for this software?
• Are you interested to apply aspect-oriented software development?
• Would you like to encapsulate error detection and corresponding exception handling as a reusable aspect here?

[oridb]

1) I already use static source code analysis where appropriate. It's often noisy and produces useless output, so it's quite time consuming. How do you think about to improve static source code analysis tools so that false positives rates are negligible? 2) No. 3) You have clearly not read and understood the code. Please don't propose changes without specifics.

[elfring]

We got different expectations around software development methodologies.