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] New: nss_parse_service_list leaks a tiny amount of memory Date: Thu, 09 Feb 2006 20:04:00 -0000 [thread overview] Message-ID: <20060209200413.2314.david@edeca.net> (raw) In nsswitch.c:519 (CVS file version 1.61), new_service is malloc()ed but never free()d. This results in minor memory leaks (~300 bytes) according to valgrind. The valgrind trace is below. I tried fixing this one myself but failed miserably :) ==2459== 312 (72 direct, 240 indirect) bytes in 2 blocks are definitely lost in loss record 3 of 11 ==2459== at 0x401B45B: malloc (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so) ==2459== by 0x43B67E8: nss_parse_service_list (nsswitch.c:519) ==2459== by 0x43B60D8: __nss_database_lookup (nsswitch.c:134) ==2459== by 0x450F1DB: ??? ==2459== by 0x451075C: ??? ==2459== by 0x43766B3: getpwnam_r@@GLIBC_2.1.2 (getXXbyYY_r.c:207) ==2459== by 0x43761CE: getpwnam (getXXbyYY.c:103) ==2459== by (my program) -- Summary: nss_parse_service_list leaks a tiny amount of memory Product: glibc Version: 2.3.6 Status: NEW Severity: minor Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: david at edeca dot net CC: glibc-bugs at sources dot redhat dot com 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 reply other threads:[~2006-02-09 20:04 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-09 20:04 david at edeca dot net [this message] 2006-02-09 20:16 ` [Bug libc/2314] " drepper at redhat dot com 2006-02-09 20:35 ` david at edeca dot net 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
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=20060209200413.2314.david@edeca.net \ --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).