From: Alan Modra <amodra@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
binutils@sourceware.org, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [RFA] bfd, compress.c (bfd_compress_section_contents): Check for out of mem.
Date: Sun, 06 Mar 2011 07:45:00 -0000 [thread overview]
Message-ID: <20110306054742.GH6275@bubble.grove.modra.org> (raw)
In-Reply-To: <4D72D6F7.1060501@vmware.com>
On Sat, Mar 05, 2011 at 04:36:07PM -0800, Michael Snyder wrote:
> * compress.c (bfd_compress_section_contents): Check for out of mem.
Just return FALSE. No need to bfd_set_error, that will already be
done in bfd_malloc. OK with that change.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2011-03-06 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 0:36 Michael Snyder
2011-03-06 7:45 ` Alan Modra [this message]
2011-03-06 18:37 ` Michael Snyder
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=20110306054742.GH6275@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=msnyder@vmware.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: 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).