Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Make solib-frv.c work in a non-FDPIC environment
Date: Thu, 20 Nov 2008 02:02:00 -0000	[thread overview]
Message-ID: <20081119142009.75faf39e@mesquite.lan> (raw)
In-Reply-To: <20081115161443.GB19656@caradoc.them.org>

On Sat, 15 Nov 2008 11:14:43 -0500
Daniel Jacobowitz <drow@false.org> wrote:

> On Fri, Nov 14, 2008 at 04:21:03PM -0700, Kevin Buettner wrote:
> > +  if (nsegs < 0)
> > +    return NULL;
> > +
> >    /* Allocate space for the complete (external) loadmap.  */
> >    ext_ldmbuf_size = sizeof (struct ext_elf32_fdpic_loadmap)
> >                 + (nsegs - 1) * sizeof (struct ext_elf32_fdpic_loadseg);
> 
> <= 0?  I realize it's probably OK in practice, assuming
> ext_elf32_fdpic_loadmap has a trailing [1] array, but allocating less
> than the size of the array would be strange.

I agree.

Here's the version that I committed:

	* solib-frv.c (fetch_loadmap): Return early when no segments are
	found.
	(frv_relocate_main_executable): Return early when both interpreter
	and executable loadmap addresses are zero.

Index: solib-frv.c
===================================================================
RCS file: /cvs/src/src/gdb/solib-frv.c,v
retrieving revision 1.22
diff -u -p -r1.22 solib-frv.c
--- solib-frv.c	26 Aug 2008 17:30:35 -0000	1.22
+++ solib-frv.c	19 Nov 2008 21:15:17 -0000
@@ -124,6 +124,9 @@ fetch_loadmap (CORE_ADDR ldmaddr)
   nsegs = extract_unsigned_integer (ext_ldmbuf_partial.nsegs,
                                     sizeof ext_ldmbuf_partial.nsegs);
 
+  if (nsegs <= 0)
+    return NULL;
+
   /* Allocate space for the complete (external) loadmap.  */
   ext_ldmbuf_size = sizeof (struct ext_elf32_fdpic_loadmap)
                + (nsegs - 1) * sizeof (struct ext_elf32_fdpic_loadseg);
@@ -860,16 +863,17 @@ static void
 frv_relocate_main_executable (void)
 {
   int status;
-  CORE_ADDR exec_addr;
+  CORE_ADDR exec_addr, interp_addr;
   struct int_elf32_fdpic_loadmap *ldm;
   struct cleanup *old_chain;
   struct section_offsets *new_offsets;
   int changed;
   struct obj_section *osect;
 
-  status = frv_fdpic_loadmap_addresses (target_gdbarch, 0, &exec_addr);
+  status = frv_fdpic_loadmap_addresses (target_gdbarch,
+                                        &interp_addr, &exec_addr);
 
-  if (status < 0)
+  if (status < 0 || (exec_addr == 0 && interp_addr == 0))
     {
       /* Not using FDPIC ABI, so do nothing.  */
       return;


      reply	other threads:[~2008-11-19 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15 18:46 Kevin Buettner
2008-11-15 22:50 ` Daniel Jacobowitz
2008-11-20  2:02   ` Kevin Buettner [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=20081119142009.75faf39e@mesquite.lan \
    --to=kevinb@redhat.com \
    --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