From: Alex Riesen <raa.lkml@gmail.com>
To: skimo@liacs.nl
Cc: Robert Watson <robert.oo.watson@gmail.com>,
git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: minor problems in git.c
Date: Thu, 1 Dec 2005 15:02:16 +0100 [thread overview]
Message-ID: <81b0412b0512010602l63ecev1ba03fb90d06e071@mail.gmail.com> (raw)
In-Reply-To: <20051201135113.GW8383MdfPADPa@greensroom.kotnet.org>
On 12/1/05, Sven Verdoolaege <skimo@kotnet.org> wrote:
> On Thu, Dec 01, 2005 at 01:48:35PM +0100, Alex Riesen wrote:
> > @@ -283,16 +283,15 @@ int main(int argc, char **argv, char **e
> > len = strlen(git_command);
> > prepend_to_path(git_command, len);
> >
> > - strncat(&git_command[len], "/git-", sizeof(git_command) - len);
> > - len += 5;
> > - strncat(&git_command[len], argv[i], sizeof(git_command) - len);
> > + snprintf(git_command + len, sizeof(git_command) - len, "/git-%s",
> > + argv[i]);
>
> Shouldn't you check the return value of snprintf
Probably. For the case where length of a git-command-name +
--exec-prefix together are longer than PATH_MAX.
> > if (access(git_command, X_OK))
> > usage(exec_path, "'%s' is not a git-command", argv[i]);
>
> or use the (possibly) truncated version of the command in the error message ?
argv[i] is the command name, already as truncated as it can possibly
be: ls-files, ls-tree, etc. Besides, the second path removes this
access check altogether:
- if (access(git_command, X_OK))
- usage(exec_path, "'%s' is not a git-command", argv[i]);
-
/* execve() can only ever return if it fails */
execve(git_command, &argv[i], envp);
- fprintf(stderr, "git: '%s': %s\n", git_command, strerror(errno));
+ if ( ENOENT == errno )
+ usage(exec_path, "'%s' is not a git-command", argv[i]);
+ else
+ fprintf(stderr, "git: '%s': %s\n", git_command, strerror(errno));
It still has the call to usage, though.
next prev parent reply other threads:[~2005-12-01 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 12:00 minor problems in git.c Robert Watson
2005-12-01 12:48 ` Alex Riesen
2005-12-01 13:51 ` Sven Verdoolaege
2005-12-01 14:02 ` Alex Riesen [this message]
2005-12-02 1:07 ` Junio C Hamano
2005-12-02 8:12 ` Alex Riesen
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=81b0412b0512010602l63ecev1ba03fb90d06e071@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=robert.oo.watson@gmail.com \
--cc=skimo@liacs.nl \
/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