public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/14104] New: Unfreed memory in sysdeps/unix/sysv/linux/check_pf.c Date: Sun, 13 May 2012 16:07:00 -0000 [thread overview] Message-ID: <bug-14104-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14104 Bug #: 14104 Summary: Unfreed memory in sysdeps/unix/sysv/linux/check_pf.c Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: unassigned@sourceware.org ReportedBy: hjl.tools@gmail.com CC: drepper.fsp@gmail.com Classification: Unclassified Since cache isn't freed in sysdeps/unix/sysv/linux/check_pf.c, "make xcheck" reports: [hjl@gnu-6 build-x86_64-linux]$ cat posix/bug-ga2-mem Memory not freed: ----------------- Address Size Caller 0x00005555557791e0 0x78 at 0x7ffff7d5d989 [hjl@gnu-6 build-x86_64-linux]$ We should add /* Make sure cache is freed before exiting. */ libc_freeres_fn (freecache) { if (cache) free (cache); } or /* Make sure cache is freed before exiting. */ libc_freeres_fn (freecache) { free (cache); } -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-05-13 16:07 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-13 16:07 hjl.tools at gmail dot com [this message] 2012-05-13 23:12 ` [Bug libc/14104] " drepper.fsp at gmail dot com 2012-05-14 19:54 ` hjl.tools at gmail dot com 2014-06-25 11:01 ` 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=bug-14104-131@http.sourceware.org/bugzilla/ \ --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).