From: Tom Tromey <tromey@redhat.com>
To: Jim Meyering <jim@meyering.net>
Cc: java-patches@gcc.gnu.org
Subject: Re: Don't leak upon failed realloc
Date: Mon, 10 Mar 2008 18:50:00 -0000 [thread overview]
Message-ID: <m363vuxxz0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87hcfhgsim.fsf@rho.meyering.net> (Jim Meyering's message of "Sat\, 08 Mar 2008 16\:11\:29 +0100")
>>>>> "Jim" == Jim Meyering <jim@meyering.net> writes:
Jim> Here are two fixes (separate patches) to avoid leaks upon failed realloc.
Jim> These are the affected files:
Thanks. This is fine, I will check it in soon.
Tom
prev parent reply other threads:[~2008-03-10 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 15:12 Jim Meyering
2008-03-10 18:50 ` Tom Tromey [this message]
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=m363vuxxz0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=java-patches@gcc.gnu.org \
--cc=jim@meyering.net \
/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: link
Be 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).