List for cgit developers and users
 help / color / mirror / Atom feed
From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: [PATCH 0/3] Fix some issues found by Coverity
Date: Sun, 17 Jan 2016 17:19:04 +0100	[thread overview]
Message-ID: <CAHmME9rVx=GjsAn7pNNS0NAJdMO869S0eGLDE9hCKfYN9s0xag@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pTUOWi1vXfnOuGZTRHuuEMs_Suta=+QRg25Ds=GG4jRw@mail.gmail.com>

So there is now only 1 issue remaining: 13839.

static void add_commit(struct string_list *authors, struct commit *commit,
        const struct cgit_period *period)
{
        struct commitinfo *info;
        struct string_list_item *author, *item;
        struct authorstat *authorstat;
        struct string_list *items;
        char *tmp;
        struct tm *date;
        time_t t;

        info = cgit_parse_commit(commit);
        tmp = xstrdup(info->author);
        author = string_list_insert(authors, tmp);
        if (!author->util)
                author->util = xcalloc(1, sizeof(struct authorstat));
        else
                free(tmp);
        authorstat = author->util;
        items = &authorstat->list;
        t = info->committer_date;
        date = gmtime(&t);
        period->trunc(date);
        tmp = xstrdup(period->pretty(date));
        item = string_list_insert(items, tmp);
        if (item->util)
                free(tmp);
        item->util++;
        authorstat->total++;
        cgit_free_commitinfo(info);
}

It doesn't like the "item->util++" line, since "if (item->util)"
implies that util could be NULL. That line doesn't make much sense to
me either. Any guesses?


Jason


  reply	other threads:[~2016-01-17 16:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16 11:03 john
2016-01-16 11:03 ` [PATCH 1/3] ui-log: handle parse_commit() errors john
2016-01-16 11:03 ` [PATCH 2/3] cache: use size_t for string lengths john
2016-01-16 11:03 ` [PATCH 3/3] cache: don't check for match with no key john
2016-01-17 16:04 ` [PATCH 0/3] Fix some issues found by Coverity Jason
2016-01-17 16:19   ` Jason [this message]
2016-01-17 20:25     ` john
2016-02-03  4:46       ` mathstuf
2016-02-08 13:35         ` Jason
2016-02-08 14:16           ` john
2016-02-08 14:33             ` Jason
2016-02-08 16:31               ` john
2016-02-08 17:26                 ` Jason

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='CAHmME9rVx=GjsAn7pNNS0NAJdMO869S0eGLDE9hCKfYN9s0xag@mail.gmail.com' \
    --to=cgit@lists.zx2c4.com \
    /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).