mirror of
https://github.com/subsurface/subsurface.git
synced 2024-11-28 05:00:20 +00:00
Deal with theoretical memory leaks
This is rather academic, but it will make Coverity happy. If we start running out of memory we should make sure we don't leak any more memory. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
This commit is contained in:
parent
20d9cf19d7
commit
3e8e005aa3
1 changed files with 6 additions and 0 deletions
6
file.c
6
file.c
|
@ -126,6 +126,12 @@ static int try_to_xslt_open_csv(const char *filename, struct memblock *mem, char
|
|||
endtag = malloc(4 + strlen(tag));
|
||||
|
||||
if (starttag == NULL || endtag == NULL) {
|
||||
/* this is fairly silly - so the malloc fails, but we strdup the error?
|
||||
* let's complete the silliness by freeing the two pointers in case one malloc succeeded
|
||||
* and the other one failed - this will make static analysis tools happy */
|
||||
free(starttag);
|
||||
free(endtag);
|
||||
free(buf);
|
||||
*error = strdup("Memory allocation failed in __func__\n");
|
||||
return 1;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue