From: "Martin Ettl" <ettl.martin@gmx.de>
To: git@vger.kernel.org
Subject: found a resource leak in file builtin-fast-export.c
Date: Thu, 09 Jul 2009 09:57:28 +0200 [thread overview]
Message-ID: <20090709075728.137880@gmx.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 464 bytes --]
Hi,
i have checked the source base of git with the static code analyis tool cppcheck. It brougt up an issue in file 1.6.3.3/builtin-fast-export.c at line 447.
The tool printed the following waring:
[git-1.6.3.3/builtin-fast-export.c:447]: (error) Resource leak: f
I have attached a patch to resolve this.
Best regards
Ettl Martin
--
Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate
für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02
[-- Attachment #2: builtin-fast-export.c.patch --]
[-- Type: text/x-patch, Size: 387 bytes --]
--- git-1.6.3.3/builtin-fast-export.c 2009-06-22 08:24:25.000000000 +0200
+++ git-1.6.3.3/builtin-fast-export_new.c 2009-07-09 09:44:28.000000000 +0200
@@ -442,8 +442,9 @@ static void export_marks(char *file)
deco++;
}
- if (ferror(f) || fclose(f))
+ if (ferror(f))
error("Unable to write marks file %s.", file);
+ fclose(f);
}
static void import_marks(char *input_file)
next reply other threads:[~2009-07-09 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 7:57 Martin Ettl [this message]
2009-07-09 8:31 ` found a resource leak in file builtin-fast-export.c Thomas Rast
2009-07-09 11:04 ` Johannes Schindelin
2009-07-09 11:24 ` Thomas Rast
2009-07-09 11:30 ` Andreas Ericsson
2009-07-09 13:01 ` Johannes Schindelin
2009-07-09 13:28 ` [PATCH] Fix export_marks() error handling Matthias Andree
2009-07-11 9:45 ` Stephen R. van den Berg
2009-07-13 8:01 ` Matthias Andree
2009-07-09 13:36 ` found a resource leak in file builtin-fast-export.c Matthias Andree
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090709075728.137880@gmx.net \
--to=ettl.martin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).