Hi,
The false positive is now fixed in upstream (few minutes ago). Expected
release date for 1.39 is November 29th.
Exactly that, cppcheck didn't spot the missing close (it was
intentional, though; it is a test case I extracted from a similar
piece of real code).
Do you perhaps mean that 1.
2009/11/4 Reijo Tomperi :
> Raphael Geissert wrote:
>
>> The attached example demonstrates a false positive and false negative I
>> found in cppcheck.
>
> Thanks, I can confirm the false positive with --all in latest trunk. Ticket
> created:
> http://sourceforge.net/apps/trac/cppcheck/ticket/896
>
Raphael Geissert wrote:
The attached example demonstrates a false positive and false negative I found
in cppcheck.
Thanks, I can confirm the false positive with --all in latest trunk.
Ticket created:
http://sourceforge.net/apps/trac/cppcheck/ticket/896
Workaround: Compare against negative v
Package: cppcheck
Version: 1.38-1
Hi,
The attached example demonstrates a false positive and false negative I found
in cppcheck.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
void c_open(void)
{
int f, fd = -1;
for (f = 0; f < 5; f++) {
4 matches
Mail list logo