Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: Michael Snyder <msnyder@redhat.com>,
	Elena Zannoni <ezannoni@redhat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [regcache] raw vs. cooked...
Date: Sun, 08 Jun 2003 22:22:00 -0000	[thread overview]
Message-ID: <3EE3B73B.9040700@redhat.com> (raw)
In-Reply-To: <002d01c32df8$866f5b50$2a00a8c0@dash>

>> > I suspect the test below is not valid for pseudo-registers, since they
>> > may not have a location in the reg cache at all.  Anyway, the change
>> > makes sh4 work again.
> 
>>
>> The check's valid.  See the thread: assertion failure in regcache.c
>> http://sources.redhat.com/ml/gdb/2003-05/msg00289.html
>>
>> Kris, Elena, did a fix get committed?
> 
> 
> I assume you're talking about the fix I described in this message:
> http://sources.redhat.com/ml/gdb/2003-05/msg00322.html
> 
> It seems like this wouldn't work for SH64 though so I was waiting until I
> had some more time to chase it. (or some SH experts piped up).  It certainly
> seems to fix the problem for 32 bit SH though.  Perhaps we could do the fix
> for all but the 64 bit version and then let someone using SH64 trip on the
> assertion and have to fix it?

To be honest, I suspect splitting sh-tdep along the lines of i386-tdep 
and x86-64-tdep might be the way to go.  Anway, yes, good suggestion,

Elena?

Andrew



      reply	other threads:[~2003-06-08 22:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-07  0:57 Michael Snyder
2003-06-08 19:06 ` Andrew Cagney
2003-06-08 19:50   ` Kris Warkentin
2003-06-08 22:22     ` Andrew Cagney [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=3EE3B73B.9040700@redhat.com \
    --to=ac131313@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kewarken@qnx.com \
    --cc=msnyder@redhat.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