public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug stdio/16734] fopen calls mmap to allocate its buffer Date: Sun, 08 Mar 2015 16:50:00 -0000 [thread overview] Message-ID: <bug-16734-131-d7jjqZtGT4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16734-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16734 --- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU C Library master sources". The branch, master has been updated via 18d26750dd8fd328a78cf639fd0ec2494680a2a4 (commit) from 9f95dc5d227c5a155d39208dfd15aacaa509b59b (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=18d26750dd8fd328a78cf639fd0ec2494680a2a4 commit 18d26750dd8fd328a78cf639fd0ec2494680a2a4 Author: Paul Pluzhnikov <ppluzhnikov@google.com> Date: Sun Mar 8 09:46:53 2015 -0700 Cleanup: in preparation for fixing BZ #16734, fix memory leaks exposed by switching fopen()ed streams from mmap to malloc. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 7 +++++++ libio/genops.c | 12 +++++------- 2 files changed, 12 insertions(+), 7 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-08 16:50 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-21 11:27 [Bug stdio/16734] New: " dancol at dancol dot org 2014-06-13 9:18 ` [Bug stdio/16734] " fweimer at redhat dot com 2015-02-14 22:55 ` ppluzhnikov at google dot com 2015-02-19 20:49 ` crrodriguez at opensuse dot org 2015-03-08 16:50 ` cvs-commit at gcc dot gnu.org [this message] 2015-06-06 9:43 ` neleai at seznam dot cz 2015-06-07 2:27 ` ppluzhnikov at google dot com 2015-08-13 1:57 ` cvs-commit at gcc dot gnu.org 2015-08-13 2:00 ` ppluzhnikov at google dot com 2015-10-29 16:28 ` jsm28 at gcc dot gnu.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-16734-131-d7jjqZtGT4@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).