git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECK

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 11, 2022, 23:07 UTC
Message-ID
<xmqqk0bvfcd6.fsf@gitster.g>
In-Reply-To
<220411.86bkx7i8qi.gmgdl@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
Show 6 quoted lines
> I wonder why we have to justify that we'll only turn on
> TEST_NO_MALLOC_CHECK if it's SANITIZE=address.
>
> I.e. we also have SANITIZE=undefined, wouldn't it be more future-proof
> to just say that these analysis options are mutually exclusive by
> default?

Given that the SANITIZE mechanism itself allows more than one to be requested at the same time, it is unclear to me why other checks like undefined needs to exclude checks done by other mechanisms like MALLOC_CHECK_ by default. If I correctly read under-the-three-dash commentary Phillip wrote, it's not like that use of MALLOC_CHECK_ inherently interferes with the way SANITIZE=undefined wants to work, no?

Previous: Ævar Arnfjörð BjarmasonNext: Ævar Arnfjörð Bjarmason
Message 4 of 5 in “tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECK”
  1. tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECKPhillip Wood via GitGitGadget, Apr 9, 2022
  2. Junio C HamanoApr 11, 2022
  3. Ævar Arnfjörð BjarmasonApr 11, 2022
  4. Junio C HamanoApr 11, 2022
  5. Ævar Arnfjörð BjarmasonApr 12, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.