Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: John Darrington <john@darrington.wattle.id.au>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] GDB: S12Z: Add assertion
Date: Tue, 20 Nov 2018 05:16:00 -0000	[thread overview]
Message-ID: <20181119221634.6feec383@pinnacle.lan> (raw)
In-Reply-To: <20181119164734.31022-1-john@darrington.wattle.id.au>

Hi John,

This is okay.  Go ahead and push it.

You leave the diff for ChangeLog out of your patches.  Just make
sure that the ChangeLog entries are placed at the top of the ChangeLog
file with  suitable header (date, name, and email) at the time that the
change is pushed.

Kevin

On Mon, 19 Nov 2018 17:47:34 +0100
John Darrington <john@darrington.wattle.id.au> wrote:

> gdb/ChangeLog:
> 
> 	* s12z-tdep.c (s12z_frame_cache): Add an assertion.
> ---
>  gdb/ChangeLog   | 8 ++++++++
>  gdb/s12z-tdep.c | 1 +
>  2 files changed, 9 insertions(+)
> 
> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
> index 4fa0b42657..990cfc3f9d 100644
> --- a/gdb/ChangeLog
> +++ b/gdb/ChangeLog
> @@ -1,3 +1,7 @@
> +2018-11-19  John Darrington <john@darrington.wattle.id.au>
> +
> +	*s12z-tdep.c (s12z_frame_cache): Add an assertion.
> +
>  2018-11-18  Tom Tromey  <tom@tromey.com>
>  
>  	PR build/23814:
> @@ -216,6 +220,10 @@
>  	frame cache, leave the frame id as the default, which is the outer
>  	frame id.
>  
> +2018-11-14  John Darrington <john@darrington.wattle.id.au>
> +
> +	* s12z-tdep.c (s12z_frame_cache): Add an assertion.
> +
>  2018-11-07  Joel Brobecker  <brobecker@adacore.com>
>  
>  	* ada-lang.c (read_atcb): Only set task_info->called_task if
> diff --git a/gdb/s12z-tdep.c b/gdb/s12z-tdep.c
> index 79f5772035..bd0bd7c001 100644
> --- a/gdb/s12z-tdep.c
> +++ b/gdb/s12z-tdep.c
> @@ -320,6 +320,7 @@ s12z_frame_cache (struct frame_info *this_frame, void **prologue_cache)
>      }
>    else
>      {
> +      gdb_assert (this_sp == this_sp_for_id);
>        /* The stack pointer of the prev frame is frame_size greater
>           than the stack pointer of this frame plus one address
>           size (caused by the JSR or BSR).  */
> -- 
> 2.11.0
> 


      reply	other threads:[~2018-11-20  5:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12  9:18 [PATCH 1/2] " John Darrington
2018-11-12  9:18 ` [PATCH 2/2] GDB: S12Z: new function s12z_extract_return_value John Darrington
2018-11-18  6:35   ` Kevin Buettner
2018-11-18  9:13     ` John Darrington
2018-11-18 18:28       ` Kevin Buettner
2018-11-20  7:56     ` [PATCH] " John Darrington
2018-11-20 16:40       ` Kevin Buettner
2018-11-20 17:01         ` John Darrington
2018-11-17 21:59 ` [PATCH 1/2] GDB: S12Z: Add assertion Kevin Buettner
2018-11-18  9:23   ` John Darrington
2018-11-18 18:42     ` Kevin Buettner
2018-11-19 16:09       ` Joel Brobecker
2018-11-19 16:47   ` [PATCH] " John Darrington
2018-11-20  5:16     ` 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=20181119221634.6feec383@pinnacle.lan \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=john@darrington.wattle.id.au \
    /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