public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david at edeca dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/2314] nss_parse_service_list leaks a tiny amount of memory Date: Thu, 09 Feb 2006 20:35:00 -0000 [thread overview] Message-ID: <20060209203545.22595.qmail@sourceware.org> (raw) In-Reply-To: <20060209200413.2314.david@edeca.net> ------- Additional Comments From david at edeca dot net 2006-02-09 20:35 ------- Apologies, this was merely a misunderstanding on my part. I had asked in #glibc whether it was unexpected behaviour and was told to bug it here. Looking again, subsequent calls do not cause it to allocate any more memory, so I can understand your point. Thanks for such a quick reply, I'll know to ignore it in future :) -- What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID http://sourceware.org/bugzilla/show_bug.cgi?id=2314 ------- 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:[~2006-02-09 20:35 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-09 20:04 [Bug libc/2314] New: " david at edeca dot net 2006-02-09 20:16 ` [Bug libc/2314] " drepper at redhat dot com 2006-02-09 20:35 ` david at edeca dot net [this message] 2007-02-04 6:12 ` john at cellform dot com 2007-02-04 6:16 ` john at cellform dot com 2007-02-16 6:51 ` drepper at redhat dot com 2007-08-23 18:30 ` drepper at redhat dot com 2010-08-08 15:21 ` andi5 dot py at gmx dot net 2010-08-08 16:04 ` andi5 dot py at gmx dot net [not found] <bug-2314-131@http.sourceware.org/bugzilla/> 2011-08-29 14:42 ` james.m.henderson at gmail dot com 2012-02-01 8:38 ` MaxZinal at yandex dot ru 2012-02-03 20:58 ` drepper.fsp at gmail dot com 2013-06-20 13:27 ` pika1021 at gmail dot com 2014-02-16 19:41 ` jackie.rosen at hushmail dot com 2014-05-28 19:46 ` schwab at sourceware dot org
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=20060209203545.22595.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).