From: "H . J . Lu" <hjl@lucon.org>
To: amodra@one.net.au
Cc: binutils@sources.redhat.com, parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: elf32-hppa: abort rather than BFD_ASSERT
Date: Thu, 24 May 2001 20:33:56 -0700 [thread overview]
Message-ID: <20010524203356.A30247@lucon.org> (raw)
In-Reply-To: <20010525130358.K9275@squeak.one.net.au>; from amodra@one.net.au on Fri, May 25, 2001 at 01:03:59PM +0930
On Fri, May 25, 2001 at 01:03:59PM +0930, amodra@one.net.au wrote:
> Be a little more brutal. Any BFD_ASSERT failure here either rapidly
> results in a segfault during linking, or worse, generates shared libs
> and executables that will bomb with bus errors at runtime. An
> undefined millicode symbol in a shared library is nasty too: they
> can't be satisfied by another shared lib export as the ABI doesn't
> allow millicode to be exported from shared libs.
>
Why not give some useful messaages? I have been doing that for new
tests I added.
H.J.
next prev parent reply other threads:[~2001-05-25 3:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 3:33 [parisc-linux] elf32-hppa: abort rather than BFD_ASSERT amodra
2001-05-25 3:33 ` H . J . Lu [this message]
2001-05-25 3:58 ` [parisc-linux] " amodra
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=20010524203356.A30247@lucon.org \
--to=hjl@lucon.org \
--cc=amodra@one.net.au \
--cc=binutils@sources.redhat.com \
--cc=parisc-linux@lists.parisc-linux.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