Completion of error handling

[elfring]

Would you like to add more error handling for return values from a function like malloc()?

[mzhukova]

Yes, this make sense, we'll take a look.

[ElenaTyuleneva]

Thanks for the suggestion, @elfring. The error handling was added throughout the library in places similar to what you pointed out. The changes are included in the following commit: [fix] Added error handling for malloc errors (#1242).

Please let us know if you have any other questions.

[elfring]

How do you think about to improve static source code analysis also for this software? :thinking:

[ElenaTyuleneva]

The team utilizes Intel-recommended static analysis tools that comprehensively scan the software for issues and vulnerabilities. We don't have any immediate plans to modify the static analysis tools used for the product. However, we appreciate your feedback and will consider it for future improvements.

[elfring]

:crystal_ball: How will chances evolve to benefit any more also from the means of aspect-oriented software development?

[ElenaTyuleneva]

@elfring , thanks for sharing your ideas! While this proposal is interesting, it diverges from the original scope of this issue. Could you please open a new issue with a detailed description of your proposal?

As there are no further questions related to the initial topic, I'm closing the current issue. We appreciate your contributions!

[elfring]

:thought_balloon: Are you aware that error detection belongs to known cross-cutting concerns?