Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Sanjoy Das <sanjoy@playingwithpointers.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Fix http://sourceware.org/bugzilla/show_bug.cgi?id=14550
Date: Mon, 24 Sep 2012 08:12:00 -0000	[thread overview]
Message-ID: <20120924081220.GB4146@adacore.com> (raw)
In-Reply-To: <1348462325-4891-2-git-send-email-sanjoy@playingwithpointers.com>

Just a request (it's OK to refuse): Can we use a different subject
for this patch? The problem with the current subject is that, when
you review the list of changes (git log), the subject isn't really
helpful in figuring out what the patch is about.

Thanks!

On Mon, Sep 24, 2012 at 10:22:03AM +0530, Sanjoy Das wrote:
> ---
>  gdb/ChangeLog |    7 +++++++
>  gdb/jit.c     |   14 ++++++++++++--
>  2 files changed, 19 insertions(+), 2 deletions(-)
> 
> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
> index 0b1d771..13eaa5c 100644
> --- a/gdb/ChangeLog
> +++ b/gdb/ChangeLog
> @@ -1,3 +1,10 @@
> +2012-09-24  Sanjoy Das <sanjoy@playingwithpointers.com>
> +
> +	PR gdb/14550
> +
> +	* jit.c (finalize_symtab): Ensure that only the global block has a
> +	NULL superblock.
> +
>  2012-09-22  Yao Qi  <yao@codesourcery.com>
>  
>  	* remote.c (remote_get_trace_status): Remove setting default
> diff --git a/gdb/jit.c b/gdb/jit.c
> index 9e8f295..eff2ed6 100644
> --- a/gdb/jit.c
> +++ b/gdb/jit.c
> @@ -724,8 +724,18 @@ finalize_symtab (struct gdb_symtab *stab, struct objfile *objfile)
>         gdb_block_iter = gdb_block_iter->next)
>      {
>        if (gdb_block_iter->parent != NULL)
> -        BLOCK_SUPERBLOCK (gdb_block_iter->real_block) =
> -          gdb_block_iter->parent->real_block;
> +	{
> +	  /* If the plugin specifically mentioned a parent block, we
> +	     use that.  */
> +	  BLOCK_SUPERBLOCK (gdb_block_iter->real_block) =
> +	    gdb_block_iter->parent->real_block;
> +	}
> +      else
> +	{
> +	  /* And if not, we set a default parent block.  */
> +	  BLOCK_SUPERBLOCK (gdb_block_iter->real_block) =
> +	    BLOCKVECTOR_BLOCK (symtab->blockvector, STATIC_BLOCK);
> +	}
>      }
>  
>    /* Free memory.  */
> -- 
> 1.7.10.4

-- 
Joel


  reply	other threads:[~2012-09-24  8:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24  4:48 [PATCH 0/3] Address review, "fix recent breakage in the JIT reader interface" Sanjoy Das
2012-09-24  4:48 ` [PATCH 2/3] Make jit-reader-load accept absolute paths to reader shared objects Sanjoy Das
2012-09-24  5:45   ` Eli Zaretskii
2012-09-27 20:58   ` Tom Tromey
2012-09-24  4:48 ` [PATCH 1/3] Fix http://sourceware.org/bugzilla/show_bug.cgi?id=14550 Sanjoy Das
2012-09-24  8:12   ` Joel Brobecker [this message]
2012-09-27 20:59   ` Tom Tromey
2012-09-24  4:48 ` [PATCH 3/3] Add a test case for the jit-reader interface Sanjoy Das
2012-09-27 21:00   ` Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2012-09-18  4:30 [PATCH 0/3] Fix recent breakage in the JIT reader interface Sanjoy Das
2012-09-18  4:30 ` [PATCH 1/3] Fix http://sourceware.org/bugzilla/show_bug.cgi?id=14550 Sanjoy Das
2012-09-18 19:37   ` Tom Tromey

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=20120924081220.GB4146@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sanjoy@playingwithpointers.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