Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch rfc, 6.0?] only allow raw raw registers; Was: [patch rfc] Add NUM_REGS pseudo regs to MIPS
Date: Wed, 20 Aug 2003 16:44:00 -0000	[thread overview]
Message-ID: <20030820164441.GA27005@nevyn.them.org> (raw)
In-Reply-To: <3F41100F.1080706@redhat.com>

On Mon, Aug 18, 2003 at 01:42:39PM -0400, Andrew Cagney wrote:
> What does "maint print [raw-]registers" look like?
> 
> >(gdb) i all-registers
> >          zero       at       v0       v1       a0       a1       a2       
> >          a3
> > R0   00000000 00000000 00000000 00000000 00000000 00000000 00000000 
> > 00000000
> >            t0       t1       t2       t3       t4       t5       t6       
> >            t7
> > R8   00000000 00000000 00000000 00000000 00000000 00000000 00000000 
> > 00000000
> >            s0       s1       s2       s3       s4       s5       s6       
> >            s7
> > R16  7fff7eaf 7fff7dcc 7fff7dd4 00000003 004059cc 10012808 00000000 
> > 00000000
> >            t8       t9       k0       k1       gp       sp       s8       
> >            ra
> > R24  00000000 00000000 00000000 00000000 00000000 7fff7df0 00000000 
> > 00000000
> >          zero       at       v0       v1       a0       a1
> >      00000000 0067194b 00000004 80279720 00000020 2aac0ac0
> > a2:  0xffffffff flt: nan               dbl: nan
> > a3:  0xffffffff flt: nan
> > t0:  0xffffffff flt: nan               dbl: nan
> > t1:  0xffffffff flt: nan
> > t2:  0xffffffff flt: nan               dbl: nan
> > t3:  0xffffffff flt: nan
> >
> >
> >Obviously the registers aren't where it expects them to be.

Thanks for the pointer, and sorry for the noise.  The problem was a
local patch which added MIPS_REGISTER_NAMES for GNU/Linux; it recently
changed to start at 32 and I still had the first 32 registers listed.

After 6.0 I'll try to flush my MIPS queue.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-08-20 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-27 18:55 Steve Watt
2003-07-27 21:23 ` Andrew Cagney
2003-07-28 15:37   ` Andrew Cagney
2003-07-28 16:38     ` Daniel Jacobowitz
2003-08-18 17:09       ` Daniel Jacobowitz
2003-08-18 17:42         ` Andrew Cagney
2003-08-20 16:44           ` Daniel Jacobowitz [this message]
2003-07-31 21:00     ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2003-07-21 22:57 Steve Watt
2003-07-27 13:50 ` [patch rfc, 6.0?] only allow raw raw registers; Was: " Andrew Cagney

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=20030820164441.GA27005@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.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