Update: Memory leaks in stdup and asprintf

[XV02]

Summary of changes

This pull request includes following changes or fixes.

• Fixes the unchanged memory allocations or return values from the functions strdup and asprintf.

Description

Most of strdups and asprintf functions had no checks on the success or failure of the action leading to potential errors, this PR adds just checks and returns errors according to the codebase section.

Type of change

• Bug fix

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have confirmed my fix is effective or that my feature works

[syaoraang]

Seems pretty good changes, but still we need a few changes.

[vandelvan]

LGTM, thanks for your contribution

[rangelmx]

LGTM!!
Thanks!

Just a question, do you have evidence of any tests performed?

[syaoraang]

Excellent work. Thanks for addressing my requests!

[amissael95]

If possible, we need to avoid the usage of "goto" for new changes. Since no loops are involved in this change we can keep as it is this time. Thanks for working on this change.

[XV02]

If possible, we need to avoid the usage of "goto" for new changes. Since no loops are involved in this change we can keep as it is this time. Thanks for working on this change.

Just for future reference, I used goto because C doesn't have a way of properly handling exceptions like other languages, goto statements used for cleanup is one of the few places where it's considered a good practice, as long as it stays local and doesn't jump upwards.