public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpyne at kde dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/10282] free() race in mcheck hooks Date: Tue, 17 Nov 2009 00:25:00 -0000 [thread overview] Message-ID: <20091117002536.1869.qmail@sourceware.org> (raw) In-Reply-To: <20090614230415.10282.pasky@suse.cz> ------- Additional Comments From mpyne at kde dot org 2009-11-17 00:25 ------- (In reply to comment #5) > That is quite strange, this appeared to me to have been fixed right before 2.11 > release. And I cannot reproduce this bug anymore with 2.11 final. Are you sure > you are seeing the bug with that glibc version? Is that vanilla or in some > distribution? Does my testcase still trigger the bug for you? This is in glibc 2.11 as distributed by Gentoo that I see it. The vanilla USE flag is disabled so they apply whatever Gentoo magic it is that makes things happen. However the mcheck fix patch applied cleanly and I can't believe Gentoo would create a patch to revert that fix. According to gitweb the affected file (malloc/hooks.c) was last updated 2009-04-17 in the glibc 2.11 tag (http://sourceware.org/git/?p=glibc.git;a=history;f=malloc/hooks.c;h=622a815f32 Your testcase still triggered the bug (and quite expeditiously too). -- http://sourceware.org/bugzilla/show_bug.cgi?id=10282 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-11-17 0:25 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-14 23:04 [Bug libc/10282] New: " pasky at suse dot cz 2009-06-14 23:05 ` [Bug libc/10282] " pasky at suse dot cz 2009-06-15 15:43 ` pasky at suse dot cz 2009-06-15 22:37 ` pasky at suse dot cz 2009-11-16 23:15 ` mpyne at kde dot org 2009-11-16 23:25 ` pasky at suse dot cz 2009-11-17 0:25 ` mpyne at kde dot org [this message] 2009-11-17 0:49 ` pasky at suse dot cz 2009-11-17 0:51 ` rdieter at math dot unl dot edu 2009-11-17 19:19 ` esigra at gmail dot com 2009-12-30 19:52 ` herrold at owlriver dot com [not found] <bug-10282-131@http.sourceware.org/bugzilla/> 2013-10-13 7:36 ` neleai at seznam dot cz 2014-02-16 19:41 ` jackie.rosen at hushmail dot com 2014-05-28 19:43 ` schwab at sourceware dot org 2014-07-01 16:37 ` fweimer at redhat dot com
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=20091117002536.1869.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).