From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-13917-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 11582 invoked by alias); 22 May 2003 19:22:42 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 11551 invoked from network); 22 May 2003 19:22:41 -0000
Received: from unknown (HELO localhost.redhat.com) (207.219.125.131)
  by sources.redhat.com with SMTP; 22 May 2003 19:22:41 -0000
Received: from redhat.com (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 6EFC12B2F; Thu, 22 May 2003 15:22:32 -0400 (EDT)
Message-ID: <3ECD2378.1040704@redhat.com>
Date: Thu, 22 May 2003 19:22:00 -0000
From: Andrew Cagney <ac131313@redhat.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kris Warkentin <kewarken@qnx.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: assertion failure in regcache.c
References: <0cd101c31fc1$b589c500$0202040a@catdog> <3ECCED6E.9060906@redhat.com> <0fb801c32095$785e5590$0202040a@catdog>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-05/txt/msg00300.txt.bz2

> Looks like you're right.  If I update to 2003-05-04 it's fine, but after
> that it blows up.  Seems to only be a problem for sh4 though.  Any
> suggestions as to what might be breaking this?  Here's the output of maint
> print registers.

>  r0b1         51   51    204       4  int
>  r1b1         52   52    208       4  int
>  r2b1         53   53    212       4  int
>  r3b1         54   54    216       4  int
>  r4b1         55   55    220       4  int
>  r5b1         56   56    224       4  int
>  r6b1         57   57    228       4  int
>  r7b1         58   58    232       4  int
>  dr0          59    0    236*1     8  double
>  dr2          60    1    244*1     8  double
>  dr4          61    2    252*1     8  double
>  dr6          62    3    260*1     8  double
>  dr8          63    4    268*1     8  double
>  dr10         64    5    276*1     8  double
>  dr12         65    6    284*1     8  double
>  dr14         66    7    292*1     8  double
>  fv0          67    8    300*1    16  *2
>  fv4          68    9    316*1    16  *2
>  fv8          69   10    332*1    16  *2
>  fv12         70   11    348*1    16  *2
> *1: Inconsistent register offsets.
> *2: Register type's name NULL.

I'd start with the obvious thing - a simple tipo in the SH4 register 
byte function.  The code was written long before these sanity checks 
were added and ``the old way'' makes it very hard to notice that the 
values are skewed.

Andrew