public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: binutils@sourceware.org
Subject: Re: ld error message %C format
Date: Wed, 18 May 2011 23:59:00 -0000	[thread overview]
Message-ID: <mcr1uzvsgqc.fsf@coign.corp.google.com> (raw)
In-Reply-To: <20110518154757.GQ20800@bubble.grove.modra.org> (Alan Modra's	message of "Thu, 19 May 2011 01:17:57 +0930")

Alan Modra <amodra@gmail.com> writes:

> How do people feel about extending typical linker error messages like
> the following
> 	tmpdir/dump0.o: In function `foo':
> 	./compressed1.c:13: undefined reference to `bar'
> to always include the section and offset information?
> 	tmpdir/dump0.o: In function `foo':
> 	./compressed1.c:13:(.text+0x8): undefined reference to `bar'
>
> When debugging toolchain problems, the section and offset is often
> more useful than the source information.  I've checked that this
> change doesn't seem to break emacs parsing of error messages.

While I'm generally not happy about adding options, I think this is a
case where we should consider it.  That is, consider an option
requesting more verbose information from linker errors.  I think that
for ordinary users of the linker, i.e., 99.9% of linker users, the
section+offset will be far more confusing than helpful.

Ian

  parent reply	other threads:[~2011-05-18 23:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 15:48 Alan Modra
2011-05-18 15:51 ` H.J. Lu
2011-05-18 16:04 ` Jason Duerstock
2011-05-18 16:19   ` Andreas Schwab
2011-05-18 23:33   ` Alan Modra
2011-05-19  0:10     ` Jason Duerstock
2011-05-18 23:59 ` Ian Lance Taylor [this message]
2011-05-20  0:00   ` Alan Modra
2011-05-20  0:24     ` Ian Lance Taylor
2011-05-23  6:13       ` Alan Modra
2011-05-24  1:24         ` Ian Lance Taylor

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=mcr1uzvsgqc.fsf@coign.corp.google.com \
    --to=iant@google.com \
    --cc=binutils@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: 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).