From: Stafford Horne <shorne@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Richard Henderson <rth@twiddle.net>,
binutils@sourceware.org, GDB patches <gdb-patches@sourceware.org>,
Openrisc <openrisc@lists.librecores.org>
Subject: Re: [PATCH 0/4] OpenRISC binutils updates and new relocs
Date: Mon, 01 Oct 2018 07:08:00 -0000 [thread overview]
Message-ID: <20181001070846.GC3318@lianli.shorne-pla.net> (raw)
In-Reply-To: <271e3bfa-4958-0387-9a82-ecfdb58f1e26@redhat.com>
On Fri, Sep 28, 2018 at 04:39:03PM +0100, Nick Clifton wrote:
>
> > To produce these errors I need to change the code, Using abort we see:
> >
> > /home/shorne/work/gnu-toolchain/local/lib/gcc/or1k-elf/9.0.0/../../../../or1k-elf/bin/ld: \
> > BFD (GNU Binutils) 2.31.51.20180927 internal error, \
> > aborting at ../../binutils-gdb/bfd/elf32-or1k.c:1152 in or1k_final_link_relocate
>
[...]
> Depending upon where you are in your code, if you have access to the link_info
> structure you can use its einfo() routine instead of bfd_error_handler. This
> has the advantage that it allows a %X formatting directive, which causes the
> program to terminate with an error exit code.
OK, thanks for the info. I tested it out using einfo(), it does exit with an
error code, but it doesn't produce the line numbers and function name that
abort() gives us. I am sure I could make it do it, but for now I will use the
error message + abort() as it gives me what I would want to see in a bug report
:).
V2 of the patch should be coming up soon.
-Stafford
prev parent reply other threads:[~2018-10-01 7:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 14:38 Stafford Horne
2018-08-21 14:39 ` [PATCH 4/4] or1k: Add the l.muld, l.muldu, l.macu, l.msbu insns Stafford Horne
2018-08-21 14:39 ` [PATCH 3/4] or1k: Add the l.adrp insn and supporting relocations Stafford Horne
2018-08-21 14:39 ` [PATCH 1/4] or1k: Add relocations for high-signed and low-stores Stafford Horne
2018-08-21 14:39 ` [PATCH 2/4] or1k: Fix messages for relocations in shared libraries Stafford Horne
2018-09-08 21:35 ` [PATCH 0/4] OpenRISC binutils updates and new relocs Stafford Horne
2018-09-17 15:07 ` Nick Clifton
2018-09-17 16:29 ` Richard Henderson
[not found] ` <20180918095234.GP4594@lianli.shorne-pla.net>
2018-09-18 11:55 ` Nick Clifton
2018-09-18 12:08 ` Joel Sherrill
2018-09-21 12:41 ` Stafford Horne
2018-09-19 13:23 ` Stafford Horne
2018-09-27 6:08 ` Stafford Horne
2018-09-28 15:39 ` Nick Clifton
2018-10-01 7:08 ` Stafford Horne [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=20181001070846.GC3318@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.com \
--cc=openrisc@lists.librecores.org \
--cc=rth@twiddle.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