From: Elia Pinto <gitter.spiros@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Ramsay Jones <ramsay@ramsay1.demon.co.uk>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH] MALLOC_CHECK: Allow checking to be disabled from config.mak
Date: Sun, 7 Oct 2012 15:13:46 +0200 [thread overview]
Message-ID: <CA+EOSBm-Z7RMb16Vk36+ek3Y1aRVTZ0mp0OPMB2iwU5_rtLOjA@mail.gmail.com> (raw)
In-Reply-To: <7vbogfquc8.fsf@alter.siamese.dyndns.org>
Hi Julio.
No, i don't know this message before. Difficult that can be related to
a recent glibc change, i think. Perhaps eglibc ? I tomorrow take a
look, i am on travel now.
Best
2012/10/6, Junio C Hamano <gitster@pobox.com>:
> Ramsay Jones <ramsay@ramsay1.demon.co.uk> writes:
>
>> The malloc checks can be disabled using the TEST_NO_MALLOC_CHECK
>> variable, either from the environment or command line of an
>> 'make test' invocation. In order to allow the malloc checks to be
>> disabled from the 'config.mak' file, we add TEST_NO_MALLOC_CHECK
>> to the environment using an export directive.
>
> We would want to encourage people to test with cheap but effective
> checks when available. I do not see "malloc: using debugging hooks"
> message anywhere when I run tests, but if you do, I'd rather see us
> check if we can tell glibc to stop doing so first without disabling
> the whole test. Your patch feels like the first step to a slipperly
> slope whose destination would make us say "we get too many messages
> so let's do nothing in "make test" with this configuration." when
> taken to the extreme, and obviously we would not want to go there
> ;-).
>
> Elia, you brought the MALLOC_CHECK_ up. Did you hear about this
> issue elsewhere before, and if you did, do you know how other
> projects solves it?
>
> Besides, doesn't a simple instruction to export TEST_NO_MALLOC_CHECK
> to your environment before running "make test" suffice?
>
>
--
Inviato dal mio dispositivo mobile
next prev parent reply other threads:[~2012-10-07 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 17:33 [PATCH] MALLOC_CHECK: Allow checking to be disabled from config.mak Ramsay Jones
2012-10-06 19:22 ` Junio C Hamano
2012-10-07 13:13 ` Elia Pinto [this message]
2012-10-08 13:19 ` Elia Pinto
2012-10-09 12:33 ` Christian Couder
2012-10-10 17:55 ` Ramsay Jones
2012-10-10 17:46 ` Ramsay Jones
2012-10-10 18:35 ` Elia Pinto
2012-10-10 18:38 ` Elia Pinto
2012-10-10 19:16 ` Junio C Hamano
2012-10-11 20:17 ` Ramsay Jones
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=CA+EOSBm-Z7RMb16Vk36+ek3Y1aRVTZ0mp0OPMB2iwU5_rtLOjA@mail.gmail.com \
--to=gitter.spiros@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ramsay@ramsay1.demon.co.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 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).