Prevent double-free strbuf when nsyms is 0 #192
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When nsyms is 0, 'last' will be equal to 'first', and strbuf will not get a new memory buf. But strbuf is not NULL now, because in the last loop, strbuf may get a memory buf allocated by 'calloc', which is only freed in the loop end but not set to NULL. If we don't set strbuf to NULL in such a case, strbuf will be double freed in the following FREEBUF(strbuf) sentence.