public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: assertion failure in regcache.c
Date: Thu, 22 May 2003 15:38:00 -0000	[thread overview]
Message-ID: <3ECCED6E.9060906@redhat.com> (raw)
In-Reply-To: <0cd101c31fc1$b589c500$0202040a@catdog>

> I just did an update and now I'm getting an assertion failure with my sh4
> port.
> 
> gdb/regcache.c:241: internal-error: init_regcache_descr: Assertion
> `descr->register_offset[i] == REGISTER_BYTE (i)' failed.
> 
> My code worked in the past few weeks so it looks like this is something
> recent.  The only change I can see to regcache.c and sh-tdep.c is to use
> DEPRECATED_REGISTER_BYTES.  Can anyone give any suggestions as to what might
> be going wrong?

Can you go back to the ``working'' code and check the output from:

	(gdb) maint print registers

(look for footnotes).  I added a sanity check with:

2003-05-04  Andrew Cagney  <cagney@redhat.com>

         * sentinel-frame.c (sentinel_frame_prev_register): Replace
         REGISTER_BYTE with register_offset_hack.
         * regcache.c (init_regcache_descr): When REGISTER_BYTE_P, check
         that REGISTER_BYTE is consistent with the regcache.
         * gdbarch.sh (REGISTER_BYTE): Add a predicate.
         * gdbarch.h, gdbarch.c: Regenerate.

however, I suspect that there has been long standing disagreement over 
the offsets only nothing was noticing it :-/

Andrew


  reply	other threads:[~2003-05-22 15:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-21 17:52 Kris Warkentin
2003-05-22 15:38 ` Andrew Cagney [this message]
2003-05-22 19:07   ` Kris Warkentin
2003-05-22 19:22     ` Andrew Cagney
2003-05-22 22:05       ` Elena Zannoni
2003-05-23 17:36         ` Kris Warkentin
2003-05-23 18:22           ` Elena Zannoni
2003-05-23 19:23             ` Kris Warkentin
2003-05-23 20:29               ` Andrew Cagney
2003-05-23 19:47             ` Andrew Cagney
2003-05-23 20:29               ` Kris Warkentin
2003-05-23 20:33                 ` Elena Zannoni
2003-05-23 20:39                   ` Kris Warkentin

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=3ECCED6E.9060906@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=kewarken@qnx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).