Package: dpkg Version: 1.16.0 Severity: minor -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi, In dpkg 1.16.0 (from git, commit: e3a9083) cppcheck was able to identify a resource leak in file_copy of src/divertcmd.c. The leak only happens on failure (hench the minor severity) and only if creat(dst, 0600) fails. In this case, file_copy will return without closing srcfd first. ~Niels - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg depends on: ii coreutils 8.5-1 GNU core utilities ii libbz2-1.0 1.0.5-6 high-quality block-sorting file co ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib ii libselinux1 2.0.96-1 SELinux runtime shared libraries ii xz-utils 5.0.0-2 XZ-format compression utilities ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 0.8.13 Advanced front-end for dpkg - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJNlemyAAoJEAVLu599gGRCjqMP/2U5yQI3lHLkNTF2d2Pd2NBR UEYnu3l51yvIrtMlrLnx9q3SDGaGEJXas6cfhxEgNEIz9/xAt3DzlDzk4HrUnkld SOrvwiQEFYcyEMuH0fMnu2hVNO20Cx4PsJePgqnls5zBxGIVH7+A/Rv9LSeta+N+ 0eyE0gud/Dt6DPFKIDzS+1I576+HY61+f8NJpK6ZWHH9SfABIj7x47JJ9ORcTIip Yrwlu6cElor53y3I+82hMni5c3F6B43t6erWL9yDVhlgL1US5sVgwffAk9JnN1Pc xXwucwb9d82T9lfdfbEQMDePwVSUHrQwmoXjRQMNbQl2XALuwERF/FqTo1WGp+w8 s3poCcS6jy8QLJAkQvILMsVvTkiqFvq6cOxBwUe9o/yXnnhSuYHlqCVh9NEEbV6e HQ2dLJD0pPG/2sDpvb2cKTYc6NWWnLh8DaGRydpgwFyMARiEAhwVhgE0cNilPvq2 JECDbrIf4NefdCm/sdj1E5a0GYP7m5E9Dp5o8+6waGRi7EHp75CY61s4/rJvSGfW ADqbc9heMAZPrmeLEE6Cd98g0t1IVyDAcTu0dF9/JoeqdAGZP/HrpDaLz+ZasYn3 ewfPGq84heaCkqgdeRoAKfazkU04oNESdRgujdxl3CsqnUKbXw42eDmXWv/Gn8D9 RvoGg7WWiaCk6wxJ/1xe =TAaa -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
