From: Derrick Stolee <derrickstolee@github.com>
To: Eric Sunshine <sunshine@sunshineco.com>,
Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] compat/win32: correct for incorrect compiler warning
Date: Tue, 19 Jul 2022 16:01:38 -0400 [thread overview]
Message-ID: <8dbcd979-0794-65c9-2192-62d4bfc8ef62@github.com> (raw)
In-Reply-To: <CAPig+cSPnQnw82DsDHhMP12sYW_XHUb6+MYt17V=0sWrW4j2iw@mail.gmail.com>
On 7/19/2022 3:48 PM, Eric Sunshine wrote:
> On Tue, Jul 19, 2022 at 2:48 PM Derrick Stolee via GitGitGadget
> <gitgitgadget@gmail.com> wrote:
>> The 'win build' job of our CI build is failing with the following error:
>>
>> compat/win32/syslog.c: In function 'syslog':
>> compat/win32/syslog.c:53:17: error: pointer 'pos' may be used after \
>> 'realloc' [-Werror=use-after-free]
>> 53 | memmove(pos + 2, pos + 1, strlen(pos));
>> CC compat/poll/poll.o
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> compat/win32/syslog.c:47:23: note: call to 'realloc' here
>> 47 | str = realloc(str, st_add(++str_len, 1));
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Removing the unrelated "CC compat/poll/poll.o" line would help make
> this output less confusing.
Yes, sorry. It's output from the parallel build that I should have noticed.
>> However, between this realloc() and the use we have a line that resets
>> the value of 'pos'. Thus, this error is incorrect. It is likely due to a
>> new version of the compiler on the CI machines.
>>
>> Instead of waiting for a new compiler, create a new variable to avoid
>> this error.
>
> If possible, it is a good idea to mention the actual compiler version
> in the commit message as an aid to future readers who might want to
> know if this sort of workaround is still needed.
I wish I knew. I can only guess that it's a new GCC version on the
Windows agents for GitHub Actions, but I don't know exactly which one.
Thanks,
-Stolee
next prev parent reply other threads:[~2022-07-19 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 18:45 [PATCH] compat/win32: correct for incorrect compiler warning Derrick Stolee via GitGitGadget
2022-07-19 19:48 ` Eric Sunshine
2022-07-19 20:01 ` Derrick Stolee [this message]
2022-07-19 20:13 ` Junio C Hamano
2022-07-21 14:17 ` Phillip Wood
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=8dbcd979-0794-65c9-2192-62d4bfc8ef62@github.com \
--to=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.