Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
To: Nicolas Blanc <nicolas.blanc@intel.com>
Cc: gdb-patches@sourceware.org, dje@google.com
Subject: Re: [PATCH v12 3/5] 'add-symbol-file' should update the current target sections.
Date: Fri, 26 Jul 2013 19:10:00 -0000	[thread overview]
Message-ID: <51F2C993.6090409@codesourcery.com> (raw)
In-Reply-To: <1374078455-906-4-git-send-email-nicolas.blanc@intel.com>

Hi Nicolas,

On 07/17/2013 01:27 PM, Nicolas Blanc wrote:
> diff --git a/gdb/symfile.c b/gdb/symfile.c
> index dbcccd3..96d9cdc 100644
> --- a/gdb/symfile.c
> +++ b/gdb/symfile.c
> @@ -57,6 +57,7 @@
>   #include "stack.h"
>   #include "gdb_bfd.h"
>   #include "cli/cli-utils.h"
> +#include "target.h"
>
>   #include <sys/types.h>
>   #include <fcntl.h>
> @@ -2158,6 +2159,51 @@ print_transfer_performance (struct ui_file *stream,
>     ui_out_text (uiout, ".\n");
>   }
>
> +/* Add the sections of OBJFILE to the current set of target sections.  */
> +
> +static void
> +add_target_sections_of_objfile (struct objfile *objfile)
> +{
> +  struct target_section_table *table = current_target_sections;
> +  struct obj_section *osect;
> +  int space;
> +  unsigned count = 0;
> +  struct target_section *ts;
> +
> +  if (objfile == NULL)
> +    return;
> +
> +  /* Compute the number of sections to add.  */
> +  ALL_OBJFILE_OSECTIONS (objfile, osect)
> +    {
> +      if (bfd_get_section_size (osect->the_bfd_section) == 0)
> +	continue;
> +      count++;
> +    }
> +
> +  if (count == 0)
> +    return;
> +
> +  space = resize_section_table (table, count);
> +
> +  ts = table->sections + space;
> +
> +  ALL_OBJFILE_OSECTIONS (objfile, osect)
> +    {
> +      if (bfd_get_section_size (osect->the_bfd_section) == 0)
> +	continue;
> +
> +      gdb_assert (ts < table->sections + space + count);
> +
> +      ts->addr = obj_section_addr (osect);
> +      ts->endaddr = obj_section_endaddr (osect);
> +      ts->the_bfd_section = osect->the_bfd_section;
> +      ts->key = (void *) objfile;
> +
> +      ts++;
> +    }
> +}
> +


This hunk needs to be updated because of this change:

2013-07-22  Doug Evans  <dje@google.com>

         * exec.h (remove_target_sections): Delete arg abfd.
         * exec.c (exec_close): Update call to remove_target_sections.
         (remove_target_sections): Delete arg abfd.
         * solib.c (update_solib_list): Ditto.
         (reload_shared_libraries_1): Ditto.
         (clear_solib): Ditto, and unconditionally call 
remove_target_sections.
         * target.h (struct target_section): Rename key to owner.
         All uses updated.

ts->key should be ts->owner now.

>   /* This function allows the addition of incrementally linked object files.
>      It does not modify any state in the target, only in the debugger.  */
>   /* Note: ezannoni 2000-04-13 This function/command used to have a
> @@ -2181,6 +2227,7 @@ add_symbol_file_command (char *args, int from_tty)
>     int expecting_sec_name = 0;
>     int expecting_sec_addr = 0;
>     char **argv;
> +  struct objfile *objf;
>
>     struct sect_opt
>     {
> @@ -2316,8 +2363,10 @@ add_symbol_file_command (char *args, int from_tty)
>     if (from_tty && (!query ("%s", "")))
>       error (_("Not confirmed."));
>
> -  symbol_file_add (filename, from_tty ? SYMFILE_VERBOSE : 0,
> -                   section_addrs, flags);
> +  objf = symbol_file_add (filename, from_tty ? SYMFILE_VERBOSE : 0,
> +			  section_addrs, flags);
> +
> +  add_target_sections_of_objfile (objf);
>
>     /* Getting new symbols may change our opinion about what is
>        frameless.  */
> @@ -3792,11 +3841,26 @@ symfile_find_segment_sections (struct objfile *objfile)
>     free_symfile_segment_data (data);
>   }
>
> +/* Listen for free_objfile events.  */
> +
> +static void
> +symfile_free_objfile (struct objfile *objfile)
> +{
> +  if (objfile == NULL)
> +    return;
> +
> +  /* Remove the target sections of user-added objfiles.  */
> +  if (objfile->flags & OBJF_USERLOADED && objfile->obfd)
> +    remove_target_sections ((void*)objfile, objfile->obfd);
> +}
> +

This hunk as well. The same change removed the second parameter of 
remove_target_sections.

With those changes i can build it cleanly.

Luis


      reply	other threads:[~2013-07-26 19:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 16:28 [PATCH v12 0/5] remove-symbol-file & add-symbol-file Nicolas Blanc
2013-07-17 16:27 ` [PATCH v12 4/5] Function is_elf_target Nicolas Blanc
2013-07-17 18:43   ` Mark Kettenis
2013-07-17 19:47     ` Doug Evans
2013-07-17 16:27 ` [PATCH v12 2/5] Documentation for the remove-symbol-file command Nicolas Blanc
2013-07-17 17:02   ` Eli Zaretskii
2013-07-17 16:27 ` [PATCH v12 1/5] New " Nicolas Blanc
2013-07-17 16:28 ` [PATCH v12 5/5] Test adding and removing a symbol file at runtime Nicolas Blanc
2013-07-17 18:53   ` Mark Kettenis
2013-07-18 12:52     ` Blanc, Nicolas
2013-07-18 13:28       ` Mark Kettenis
2013-07-18 16:05         ` Blanc, Nicolas
2013-07-17 16:28 ` [PATCH v12 3/5] 'add-symbol-file' should update the current target sections Nicolas Blanc
2013-07-26 19:10   ` Luis Machado [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=51F2C993.6090409@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nicolas.blanc@intel.com \
    /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