public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper 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: Sun, 06 Sep 2009 13:16:00 -0000 [thread overview]
Message-ID: <20090906131638.23554.qmail@sourceware.org> (raw)
In-Reply-To: <20090905210537.10610.laurent.deniau@cern.ch>
------- Additional Comments From drepper at redhat dot com 2009-09-06 13:16 -------
This is no self-contained test. Who knows what this library does. This is
where the problem seems to be. Otherwise, produce a test case which doesn't
rely on anything but libc.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
GCC build triplet| gcc -v Using built-in |gcc -v Using built-in specs.
|specs. Target: x86_64-linux-|Target: x86_64-linux-gnu
|gnu Configure |Configure
http://sourceware.org/bugzilla/show_bug.cgi?id=10610
------- 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-09-06 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-05 21:05 [Bug libc/10610] New: " laurent dot deniau at cern dot ch
2009-09-06 13:16 ` drepper at redhat dot com [this message]
2009-10-28 13:46 ` [Bug libc/10610] " 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
[not found] <bug-10610-131@http.sourceware.org/bugzilla/>
2011-09-12 9:19 ` spoyarek at redhat dot com
2011-10-07 14:59 ` drepper.fsp at gmail dot com
2014-07-01 6:54 ` 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=20090906131638.23554.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: 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).