Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • stable-1.12
  • pbalcer-valgrind-update
  • stable-1.9
  • gh-pages-old
  • stable-1.11
  • stable-1.10
  • stable-1.8
  • stable-1.7
  • stable-1.6
  • stable-1.5
  • stable-1.4
  • stable-1.3
  • stable-1.2
  • 1.12.0-rc1
  • 1.11.1
  • 1.10.1
  • 1.9.3
  • 1.10.1-rc2
  • 1.9.3-rc2
  • 1.11.1-rc1
  • 1.10.1-rc1
  • 1.9.3-rc1
  • 1.11.0
  • 1.11.0-rc2
  • 1.11.0-rc1
  • 1.9.2
  • 1.10
  • 1.10-rc1
  • 1.9.1
  • 1.8.1
  • 1.7.1
  • 1.9
  • 1.9-rc2
34 results
Blame Permalink
  • Adam Borowski's avatar
    b2c565ec
    test: don't use a FILE pointer after fclose · b2c565ec
    Adam Borowski authored 
    GCC 12 considers this wrong:
ut_file.c:92:17: error: pointer ‘stream’ may be used after ‘fclose’
    [-Werror=use-after-free]
In our case the pointer doesn't actually get dereferenced -- but then,
knowing its no longer valid value doesn't help in debugging, thus
there's no point in arguing with the compiler.
    b2c565ec
    History
    test: don't use a FILE pointer after fclose
    Adam Borowski authored 
    GCC 12 considers this wrong:
ut_file.c:92:17: error: pointer ‘stream’ may be used after ‘fclose’
    [-Werror=use-after-free]
In our case the pointer doesn't actually get dereferenced -- but then,
knowing its no longer valid value doesn't help in debugging, thus
there's no point in arguing with the compiler.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.