public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dbavatar at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/16001] New: calls to getaddrinfo() leak memory. Date: Fri, 04 Oct 2013 20:14:00 -0000 [thread overview] Message-ID: <bug-16001-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16001 Bug ID: 16001 Summary: calls to getaddrinfo() leak memory. Product: glibc Version: 2.18 Status: NEW Severity: normal Priority: P2 Component: network Assignee: unassigned at sourceware dot org Reporter: dbavatar at gmail dot com Created attachment 7223 --> https://sourceware.org/bugzilla/attachment.cgi?id=7223&action=edit Leak test case. Calls to getaddrinfo() followed by freeaddrinfo() leak memory. Test case attached. Sending fix patch to libc-alpha. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-10-04 20:14 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-04 20:14 dbavatar at gmail dot com [this message] 2014-06-05 14:24 ` [Bug network/16001] " schwab@linux-m68k.org 2014-06-05 16:04 ` dbavatar at gmail dot com 2014-06-13 12:43 ` fweimer at redhat dot com 2014-09-29 8:17 ` aoliva at sourceware dot org 2014-10-13 3:12 ` dbavatar at gmail dot com 2014-10-31 7:27 ` aoliva at sourceware dot org 2014-10-31 8:12 ` aoliva 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=bug-16001-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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).