PR analyzer/98575 describes an unexpected -Wanalyzer-malloc-leak false
positive from gcc.dg/analyzer/pr94851-1.c on glibc < 2.28.
The issue is that a getchar call gets inlined into a call to _IO_getc,
and "_IO_getc" is not in the set of FILE * functions the analyzer
"knows about". This exposes a bug in memory leak detection on code
paths in which an unknown function has been called.
The memory leak bug is fixed in the prior commit, but for good
measure this patch special-cases the "_IO_"-prefixed names in glibc
so that the analyzer can reuse its knowledge about the unprefixed
variants.
gcc/analyzer/ChangeLog:
PR analyzer/98575
* sm-file.cc (is_file_using_fn_p): Support "_IO_"-prefixed
variants.
gcc/testsuite/ChangeLog:
PR analyzer/98575
* gcc.dg/analyzer/file-1.c (test_5): New.
* gcc.dg/analyzer/file-3.c: New test.
is_file_using_fn_p (tree fndecl)
{
function_set fs = get_file_using_fns ();
- return fs.contains_decl_p (fndecl);
+ if (fs.contains_decl_p (fndecl))
+ return true;
+
+ /* Also support variants of these names prefixed with "_IO_". */
+ const char *name = IDENTIFIER_POINTER (DECL_NAME (fndecl));
+ if (strncmp (name, "_IO_", 4) == 0)
+ if (fs.contains_name_p (name + 4))
+ return true;
+
+ return false;
}
/* Implementation of state_machine::on_stmt vfunc for fileptr_state_machine. */
return; /* { dg-warning "leak of FILE 'f'" } */
}
+
+void
+test_5 (const char *path)
+{
+ FILE *f = fopen (path, "r"); /* { dg-message "opened here" } */
+ return; /* { dg-warning "leak of FILE 'f'" } */
+}
--- /dev/null
+typedef struct _IO_FILE FILE;
+extern struct _IO_FILE *stderr;
+
+extern FILE *fopen (const char *__restrict __filename,
+ const char *__restrict __modes);
+extern int _IO_getc (FILE *stream);
+
+void
+test_1 (const char *path)
+{
+ FILE *f = fopen (path, "r"); /* { dg-message "opened here" } */
+
+ /* Implementation of getc in glibc < 2.28.
+ Verify that we know that this doesn't close the file. */
+ _IO_getc (f);
+
+ return; /* { dg-warning "leak of FILE 'f'" } */
+}