public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: tromey@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM]  archer-tromey-remove-obj_section: hack that makes somread.c not cause simple crashes
Date: Tue, 18 Dec 2012 18:31:00 -0000	[thread overview]
Message-ID: <20121218183120.5685.qmail@sourceware.org> (raw)

The branch, archer-tromey-remove-obj_section has been updated
       via  91ca1b7f115b2ff6d2099293d7776dbc809003fc (commit)
       via  5fc3d89349880eade3274048ee973711e6f407de (commit)
      from  f95dc0c957ad8c479e5759c18584a41253881ae6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email.

- Log -----------------------------------------------------------------
commit 91ca1b7f115b2ff6d2099293d7776dbc809003fc
Author: Tom Tromey <tromey@redhat.com>
Date:   Tue Dec 18 11:31:08 2012 -0700

    hack that makes somread.c not cause simple crashes

commit 5fc3d89349880eade3274048ee973711e6f407de
Author: Tom Tromey <tromey@redhat.com>
Date:   Tue Dec 18 11:30:47 2012 -0700

    fix crash with multi-target bfd and som

-----------------------------------------------------------------------

Summary of changes:
 bfd/som.c     |    3 ++-
 gdb/somread.c |    2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

First 500 lines of diff:
diff --git a/bfd/som.c b/bfd/som.c
index efaf400..f0ef8dc 100644
--- a/bfd/som.c
+++ b/bfd/som.c
@@ -2686,7 +2686,8 @@ som_is_subspace (asection *section)
 {
   /* If no copy data is available, then it's neither a space nor a
      subspace.  */
-  if (som_section_data (section)->copy_data == NULL)
+  if (som_section_data (section) == NULL
+      || som_section_data (section)->copy_data == NULL)
     return FALSE;
 
   /* If the containing space is the same as the given section,
diff --git a/gdb/somread.c b/gdb/somread.c
index 29910af..5f9e185 100644
--- a/gdb/somread.c
+++ b/gdb/somread.c
@@ -378,7 +378,7 @@ som_symfile_offsets (struct objfile *objfile, struct section_addr_info *addrs)
     obstack_alloc (&objfile->objfile_obstack, 
 		   SIZEOF_N_SECTION_OFFSETS (objfile->num_sections));
 
-  sect = bfd_get_section_by_name (objfile->obfd, "$TEXT$");
+  sect = bfd_get_section_by_name (objfile->obfd, "$CODE$");
   if (sect != NULL)
     objfile->sect_index_text = sect->index;
   sect = bfd_get_section_by_name (objfile->obfd, "$DATA$");


hooks/post-receive
--
Repository for Project Archer.


                 reply	other threads:[~2012-12-18 18:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20121218183120.5685.qmail@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=archer-commits@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).