From: "Jonas Fonseca" <jonas.fonseca@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <junkio@cox.net>
Subject: Re: [PATCH] branch: fix segfault when resolving an invalid HEAD
Date: Sun, 20 May 2007 14:44:47 +0200 [thread overview]
Message-ID: <2c6b72b30705200544g2f9cb67eod5ea9342c3fda2a5@mail.gmail.com> (raw)
In-Reply-To: <20070520121917.GA18850@diku.dk>
On 5/20/07, Jonas Fonseca <fonseca@diku.dk> wrote:
> Caused by return value of resolve_ref being passed directly
> to xstrdup whereby the sanity checking was never reached.
While checking other usage of resolve_ref, this problem also occurs in
builtin-show-branch.c around line 695, however, the logic later in the
file seems to be more forgiving so I have no idea of how to patch it.
--
Jonas Fonseca
prev parent reply other threads:[~2007-05-20 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 12:19 [PATCH] branch: fix segfault when resolving an invalid HEAD Jonas Fonseca
2007-05-20 12:44 ` Jonas Fonseca [this message]
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=2c6b72b30705200544g2f9cb67eod5ea9342c3fda2a5@mail.gmail.com \
--to=jonas.fonseca@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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