From: Junio C Hamano <gitster@pobox.com>
To: "Phillip Wood via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Elia Pinto" <gitter.spiros@gmail.com>,
"Phillip Wood" <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH] tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECK
Date: Mon, 11 Apr 2022 12:11:19 -0700 [thread overview]
Message-ID: <xmqqtuazh1uw.fsf@gitster.g> (raw)
In-Reply-To: <pull.1210.git.1649507317350.gitgitgadget@gmail.com> (Phillip Wood via GitGitGadget's message of "Sat, 09 Apr 2022 12:28:37 +0000")
"Phillip Wood via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Phillip Wood <phillip.wood@dunelm.org.uk>
>
> As the address sanitizer checks for a superset of the issues detected
> by setting MALLOC_CHECK_ (which tries to detect things like double
> frees and off-by-one errors) there is no need to set the latter when
> compiling with -fsanitize=address.
Very good idea.
> I'm submitting this now as it fixes a regression introduced in the
> current cycle. Having said that there is an easy workaround (once one
> has discovered GIT_TEST_NO_MALLOC_CHECK) so I'd be happy to wait until
> the start of the next cycle given I've just missed -rc1.
Yeah, if this patch were broken, we'd be in worse place than we
currently are, so I'd rather not fast-track it. I will queue it in
'seen' and possibly merge to 'next' as it is a good idea to avoid
using both at the same time, though.
Thanks.
next prev parent reply other threads:[~2022-04-11 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 12:28 [PATCH] tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECK Phillip Wood via GitGitGadget
2022-04-11 19:11 ` Junio C Hamano [this message]
2022-04-11 21:50 ` Ævar Arnfjörð Bjarmason
2022-04-11 23:07 ` Junio C Hamano
2022-04-12 7:44 ` Ævar Arnfjörð Bjarmason
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=xmqqtuazh1uw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitter.spiros@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/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.