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 nptl/5171] Memory leak in nptl pthread_create() call Date: Mon, 15 Oct 2007 04:04:00 -0000 [thread overview] Message-ID: <20071015040409.19593.qmail@sourceware.org> (raw) In-Reply-To: <20071013011337.5171.apconole@yahoo.com> ------- Additional Comments From drepper at redhat dot com 2007-10-15 04:04 ------- There are no known leaks. Aside from the fact that you're using an ancient glibc version there are other possibilities - valgrind gets it wrong. This can happen in lowlevel code like glibc - you mistake memory which cannot be freed until the end for a memory leak. This is not the same Get the most recent glibc and provide a self-contained test case. Until then I close the bug. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME http://sourceware.org/bugzilla/show_bug.cgi?id=5171 ------- 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:[~2007-10-15 4:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-13 1:13 [Bug nptl/5171] New: " apconole at yahoo dot com 2007-10-15 4:04 ` drepper at redhat dot com [this message] 2009-01-29 16:05 ` [Bug nptl/5171] " vgabor at gmail dot com 2009-01-29 16:35 ` drepper at redhat dot com [not found] <bug-5171-131@http.sourceware.org/bugzilla/> 2014-02-16 19:40 ` jackie.rosen at hushmail dot com 2014-05-28 19:45 ` schwab at sourceware dot org 2014-07-04 7:21 ` 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=20071015040409.19593.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).