git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Fleischer <git@cryptocrack.de>
To: Mike Hommey <mh@glandium.org>, git@vger.kernel.org
Cc: "Jeff King" <peff@peff.net>
Subject: Re: use-after-free leads to git-blame writing garbage in error message
Date: Tue, 03 Feb 2015 10:32:45 +0100	[thread overview]
Message-ID: <20150203093245.3733.71523@typhoon> (raw)
In-Reply-To: <20150203091715.GA25445@glandium.org>

On Tue, 03 Feb 2015 at 10:17:15, Mike Hommey wrote:
> Symptoms:
>   $ git blame HEAD -- foo
>   fatal: no such path foo in <random garbage>
> 
> Expected output:
>   $ git blame HEAD -- foo
>   fatal: no such path foo in HEAD
> 
> Bisect says this was introduced in 1da1e07c835e900337714cfad6c32a8dc0b36ac3
> [...]

This should be fixed by commit a46442f (blame.c: fix garbled error
message, 2015-01-12) which is in next.

  reply	other threads:[~2015-02-03  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03  9:17 use-after-free leads to git-blame writing garbage in error message Mike Hommey
2015-02-03  9:32 ` Lukas Fleischer [this message]
2015-02-03  9:38   ` Mike Hommey

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=20150203093245.3733.71523@typhoon \
    --to=git@cryptocrack.de \
    --cc=git@vger.kernel.org \
    --cc=mh@glandium.org \
    --cc=peff@peff.net \
    /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).