Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#14126 - bzip2 contains resource leaks
Attached to Project:
Arch Linux
Opened by BillE (boogachamp) - Monday, 06 April 2009, 18:45 GMT
Last edited by Aaron Griffin (phrakture) - Thursday, 09 April 2009, 17:25 GMT
Opened by BillE (boogachamp) - Monday, 06 April 2009, 18:45 GMT
Last edited by Aaron Griffin (phrakture) - Thursday, 09 April 2009, 17:25 GMT
|
DetailsDescription:
I couldn't find where to report bugs directly to bzip2 devs, so I am posting it here because its the disto I use. Running cppcheck 1.30 against bzip2 1.0.5 yeilds: % cppcheck -f -a -q . [./bzip2.c:1309]: (error) Resource leak: inStr [./bzip2.c:1596]: (error) Resource leak: inStr inStr should be closed before leaving these functions. |
This task depends upon
Comment by Gerardo Exequiel Pozzi (djgera) -
Monday, 06 April 2009, 21:43 GMT
Hi, send mail to the author, look the mail at http://www.bzip.org
Comment by BillE (boogachamp) -
Monday, 06 April 2009, 22:07 GMT
done and done
Comment by Aaron Griffin (phrakture) -
Thursday, 09 April 2009, 17:25 GMT
Yeah, no point in tracking this in the Arch bug tracker - it fractures the information. Upstream bugs should always be sent upstream - closing