• Jeff King's avatar
    prefix_filename: return newly allocated string · e4da43b1
    Jeff King authored
    The prefix_filename() function returns a pointer to static
    storage, which makes it easy to use dangerously. We already
    fixed one buggy caller in hash-object recently, and the
    calls in apply.c are suspicious (I didn't dig in enough to
    confirm that there is a bug, but we call the function once
    in apply_all_patches() and then again indirectly from
    Let's make it harder to get wrong by allocating the return
    value. For simplicity, we'll do this even when the prefix is
    empty (and we could just return the original file pointer).
    That will cause us to allocate sometimes when we wouldn't
    otherwise need to, but this function isn't called in
    performance critical code-paths (and it already _might_
    allocate on any given call, so a caller that cares about
    performance is questionable anyway).
    The downside is that the callers need to remember to free()
    the result to avoid leaking. Most of them already used
    xstrdup() on the result, so we know they are OK. The
    remainder have been converted to use free() as appropriate.
    I considered retaining a prefix_filename_unsafe() for cases
    where we know the static lifetime is OK (and handling the
    cleanup is awkward). This is only a handful of cases,
    though, and it's not worth the mental energy in worrying
    about whether the "unsafe" variant is OK to use in any
    Signed-off-by: 's avatarJeff King <peff@peff.net>
    Signed-off-by: 's avatarJunio C Hamano <gitster@pobox.com>
worktree.c 10.2 KB