public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spoyarek at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/10610] valgrind detect 1 extra free() from _vgnU_freeres per shared lib linked
Date: Mon, 12 Sep 2011 09:19:00 -0000 [thread overview]
Message-ID: <bug-10610-131-Et04ASvYuv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10610-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=10610
Siddhesh Poyarekar <spoyarek at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |spoyarek at redhat dot com
--- Comment #6 from Siddhesh Poyarekar <spoyarek at redhat dot com> 2011-09-12 09:18:14 UTC ---
Looks like this has been fixed already with
bc5fb0374c3ce6eca92f44d13a55b066e707c4a0 . It was reported in Fedora too:
https://bugzilla.redhat.com/show_bug.cgi?id=629976
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next parent reply other threads:[~2011-09-12 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10610-131@http.sourceware.org/bugzilla/>
2011-09-12 9:19 ` spoyarek at redhat dot com [this message]
2011-10-07 14:59 ` drepper.fsp at gmail dot com
2014-07-01 6:54 ` fweimer at redhat dot com
2009-09-05 21:05 [Bug libc/10610] New: " laurent dot deniau at cern dot ch
2009-09-06 13:16 ` [Bug libc/10610] " drepper at redhat dot com
2009-10-28 13:46 ` schwab at linux-m68k dot org
2009-10-30 4:03 ` drepper at redhat dot com
2010-06-30 8:22 ` caolanm at redhat dot com
2010-06-30 8:23 ` caolanm at redhat dot com
2010-06-30 8:27 ` caolanm 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=bug-10610-131-Et04ASvYuv@http.sourceware.org/bugzilla/ \
--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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).