[Bug analyzer/99716] -Wanalyzer-double-fclose when fclose is called inside a loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99716 David Malcolm changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug analyzer/99716] -Wanalyzer-double-fclose when fclose is called inside a loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99716 --- Comment #5 from CVS Commits --- The master branch has been updated by David Malcolm : https://gcc.gnu.org/g:71fc4655ab86ab66b40165b2cb49c1395ca82a9a commit r11-7820-g71fc4655ab86ab66b40165b2cb49c1395ca82a9a Author: David Malcolm Date: We

[Bug analyzer/99716] -Wanalyzer-double-fclose when fclose is called inside a loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99716 --- Comment #4 from David Malcolm --- (In reply to David Malcolm from comment #2) > Also, I think we're missing a warning about "fp" possibly being NULL, for > the case where the fopen fails. I've filed this as bug 99738.

[Bug analyzer/99716] -Wanalyzer-double-fclose when fclose is called inside a loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99716 --- Comment #3 from Richard W.M. Jones --- FYI the original code is: https://github.com/libguestfs/libguestfs/blob/e0a11061035d47b118c95706240bcc17fd576edc/tests/mount-local/test-parallel-mount-local.c#L299-L335

[Bug analyzer/99716] -Wanalyzer-double-fclose when fclose is called inside a loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99716 David Malcolm changed: What|Removed |Added Last reconfirmed||2021-03-23 Ever confirmed|0

[Bug analyzer/99716] -Wanalyzer-double-fclose when fclose is called inside a loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99716 --- Comment #1 from David Malcolm --- Thanks. Looks very similar to bug 93695 - the analyzer "gets confused" in how it tracks allocations in a loop (albeit with a different kind of resource, and thus worth tracking as a separate bug).