From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: binutils@sourceware.org
Cc: gdb-patches@sourceware.org
Subject: [PATCH] MIPS/BFD: Fix assertions with SGI IRIX files
Date: Thu, 18 Aug 2011 16:41:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1108181530580.4083@tp.orcam.me.uk> (raw)
Hello,
If an SGI IRIX ELF variation binary (also produced by binutils for some
target configurations) is loaded into GDB configured for the traditional
MIPS ELF variation, then a load of assertion failures is spat. They
actually come from BFD being confused.
As no user input, however unreasonable, should ever trigger assertions
and this is simply a case of an unsupported binary format, here's a fix to
convert the offending code to do proper error reporting instead.
Verified manually with GDB, the error messages are produced. I was
unable to trigger this problem with the linker, even though this piece of
code looks reachable within to me.
OK to apply?
2011-08-18 Maciej W. Rozycki <macro@codesourcery.com>
bfd/
* elfxx-mips.c (_bfd_mips_elf_symbol_processing): Replace
assertions with warning messages.
Maciej
binutils-mips-sgi-err.diff
Index: binutils-fsf-trunk-quilt/bfd/elfxx-mips.c
===================================================================
--- binutils-fsf-trunk-quilt.orig/bfd/elfxx-mips.c 2011-08-03 14:02:30.000000000 +0100
+++ binutils-fsf-trunk-quilt/bfd/elfxx-mips.c 2011-08-03 14:04:07.000000000 +0100
@@ -6350,7 +6350,10 @@ _bfd_mips_elf_symbol_processing (bfd *ab
{
asection *section = bfd_get_section_by_name (abfd, ".text");
- BFD_ASSERT (SGI_COMPAT (abfd));
+ if (!SGI_COMPAT (abfd))
+ _bfd_error_handler (_("%B: Warning: SGI IRIX format special section "
+ "%s unsupported with the selected emulation"),
+ abfd, "MIPS_TEXT");
if (section != NULL)
{
asym->section = section;
@@ -6366,7 +6369,10 @@ _bfd_mips_elf_symbol_processing (bfd *ab
{
asection *section = bfd_get_section_by_name (abfd, ".data");
- BFD_ASSERT (SGI_COMPAT (abfd));
+ if (!SGI_COMPAT (abfd))
+ _bfd_error_handler (_("%B: Warning: SGI IRIX format special section "
+ "%s unsupported with the selected emulation"),
+ abfd, "MIPS_DATA");
if (section != NULL)
{
asym->section = section;
next reply other threads:[~2011-08-18 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 16:41 Maciej W. Rozycki [this message]
[not found] <alpine.DEB.1.10.1108181530580.4083__36247.0631408089$1313685694$gmane$org@tp.orcam.me.uk>
2011-08-19 9:42 ` Richard Sandiford
2011-08-31 18:01 ` Maciej W. Rozycki
2011-08-31 20:14 ` Richard Sandiford
2011-09-02 10:06 ` Maciej W. Rozycki
2011-10-24 14:02 ` Maciej W. Rozycki
2011-11-15 17:29 ` Richard Sandiford
2011-11-16 12:37 ` Maciej W. Rozycki
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=alpine.DEB.1.10.1108181530580.4083@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@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