Re: [PATCH 0/10] towards clean leak-checker output
- Date: Tue, 5 Sep 2017 15:02:12 -0400
- From: Jeff King <peff@xxxxxxxx>
- Subject: Re: [PATCH 0/10] towards clean leak-checker output
On Tue, Sep 05, 2017 at 07:50:10PM +0200, Martin Ågren wrote:
> > That line is the setting of argv0_path, which is a global (and thus
> > shouldn't be marked as leaking). Interestingly, it only happens with
> > -O2. Compiling with -O0 works fine. I'm not sure if it's a bug or
> > what.
> > I did most of my testing with clang-6.0, which gets this case right.
> Hmmm, I got the same wrong results (IMHO) from Valgrind, which
> classified this as "definitely lost". Like you I found that -O0 helped.
> And yes, that was with gcc. Maybe gcc with optimization somehow manages
> to hide the pointers from these tools. I know too little about the
> technical details to have any real ideas, though. My searches did not
> bring up anything useful. (gcc 5.4.0)
Yeah, I think it is just optimizing out the variable entirely. If
RUNTIME_PREFIX isn't defined (and it's not for non-Windows platforms)
then we never look at the variable at all, and it's a dead assignment.
And the compiler can see that easily because it's got static linkage. So
it drops the variable completely, but it can't drop the call to
xstrdup() with the information in exec_cmd.c. It has to call the
function and throw away the result, resulting in the leak.
In fact, the whole extract_argv0_path thing is pointless without
RUNTIME_PREFIX. So I think one reasonable fix is just:
diff --git a/exec_cmd.c b/exec_cmd.c
index fb94aeba9c..09f05c3bc3 100644
@@ -5,7 +5,10 @@
#define MAX_ARGS 32
static const char *argv_exec_path;
static const char *argv0_path;
char *system_path(const char *path)
@@ -40,6 +43,7 @@ char *system_path(const char *path)
void git_extract_argv0_path(const char *argv0)
const char *slash;
if (!argv0 || !*argv0)
@@ -49,6 +53,7 @@ void git_extract_argv0_path(const char *argv0)
argv0_path = xstrndup(argv0, slash - argv0);
void git_set_argv_exec_path(const char *exec_path)