From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: John Darrington <john@darrington.wattle.id.au>
Subject: Re: [PATCH 1/2] GDB: S12Z: Add assertion
Date: Sat, 17 Nov 2018 21:59:00 -0000 [thread overview]
Message-ID: <20181117145928.726522e6@pinnacle.lan> (raw)
In-Reply-To: <20181112091721.28040-1-john@darrington.wattle.id.au>
On Mon, 12 Nov 2018 10:17:20 +0100
John Darrington <john@darrington.wattle.id.au> wrote:
> ---
> gdb/s12z-tdep.c | 1 +
> 1 file changed, 1 insertion(+)
>
> 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). */
> --
Could you please add a ChangeLog entry?
Also, on the same topic, what happened to the ChangeLog entries
for the initial commit / push of the s12z port? (I don't see them
in the ChangeLog file.)
As for adding the assert, I suppose that you're just reminding the
reader of this earlier assignment? ...
this_sp_for_id = this_sp;
(I didn't see anything which might change either this_sp or
this_sp_for_id along the code path leading to the assert.)
Kevin
next prev parent reply other threads:[~2018-11-17 21:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 9:18 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 ` Kevin Buettner [this message]
2018-11-18 9:23 ` [PATCH 1/2] GDB: S12Z: Add assertion 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
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=20181117145928.726522e6@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