git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Elia Pinto <gitter.spiros@gmail.com>
Cc: 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: Tue, 9 Oct 2012 14:33:15 +0200	[thread overview]
Message-ID: <CAP8UFD2k9HjAKq-1WrRpk3NtqWnewDmqT0dqKfN9vYDk9fnBQg@mail.gmail.com> (raw)
In-Reply-To: <CA+EOSBnKqkQ_nLyEKzxsMYnB04X9ABMp3P3CuDy3ohfcoEbQtA@mail.gmail.com>

Hi,

On Mon, Oct 8, 2012 at 3:19 PM, Elia Pinto <gitter.spiros@gmail.com> wrote:
> Ok. I have found. For me this is not a problem any more these days.
> Was fixed in glibc 2.8.90-9 2008
>
> * Wed Jul 16 2008 Jakub Jelinek <jakub@redhat.com> 2.8.90-9
> - update from trunk
>   - fix unbuffered vfprintf if writing to the stream fails (#455360)
>   - remove useless "malloc: using debugging hooks" message (#455355)
>   - nscd fixes
> (from glibc rpm changelog)
>
> This is the bugzilla filled and closed
> https://bugzilla.redhat.com/show_bug.cgi?id=455355
>
> Ramsay, what version of glibc you have and in what distro? thanks

I have the same problem on a RHEL 5.3 (2.6.18-128.el5 #1 SMP Wed Dec
17 11:41:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux) with
glibc-2.5-34.

Best,
Christian.

  reply	other threads:[~2012-10-09 12:33 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
2012-10-08 13:19   ` Elia Pinto
2012-10-09 12:33     ` Christian Couder [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP8UFD2k9HjAKq-1WrRpk3NtqWnewDmqT0dqKfN9vYDk9fnBQg@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=gitter.spiros@gmail.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).