From: Alan Modra <amodra@gmail.com>
To: Chen Gang <xili_gchen_5257@hotmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] ld/ldmain.c (main): Use %F instead of %X for einfo().
Date: Wed, 18 Mar 2015 01:18:00 -0000 [thread overview]
Message-ID: <20150318011803.GC24573@bubble.grove.modra.org> (raw)
In-Reply-To: <BLU436-SMTP1361F406467D82A57C8069AB9030@phx.gbl>
On Wed, Mar 18, 2015 at 07:54:46AM +0800, Chen Gang wrote:
> When src or dst is NULL, the next fread or fwrite will cause segment
> fault, so we need treat it as fatal case in einfo().
>
> 2015-03-18 Chen Gang <gang.chen.5i5j@gmail.com>
>
> * ldmain.c (main): Use %F instead of %X for einfo().
Thanks, committed.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2015-03-18 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 23:55 Chen Gang
2015-03-18 1:18 ` Alan Modra [this message]
[not found] <BLU436-SMTP1074DBE9281017DAB4DB3A9B9000@phx.gbl>
2015-03-18 10:32 ` Chen Gang
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=20150318011803.GC24573@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=xili_gchen_5257@hotmail.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).