From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com, cagney@redhat.com
Subject: Re: [patch rfc, 6.0?] only allow raw raw registers; Was: [patch rfc] Add NUM_REGS pseudo regs to MIPS
Date: Mon, 18 Aug 2003 17:09:00 -0000 [thread overview]
Message-ID: <20030818170933.GA26128@nevyn.them.org> (raw)
In-Reply-To: <20030728163857.GA28595@nevyn.them.org>
On Mon, Jul 28, 2003 at 12:38:57PM -0400, Daniel Jacobowitz wrote:
> On Mon, Jul 28, 2003 at 11:37:12AM -0400, Andrew Cagney wrote:
> > I've checked this tweak into 6.0 and mainline:
> >
> > >2003-07-27 Andrew Cagney <cagney@redhat.com>
> > >
> > > * mips-tdep.c (print_gp_register_row): Print the GPR's register
> > > MOD NUM_REGS.
> > >
> >
> > and this change into just the mainline (6.0 will follow in a few days if
> > no one notices a problem):
> >
> > >2003-07-27 Andrew Cagney <cagney@redhat.com>
> > >
> > > * regcache.c (struct regcache_descr): Update comments on
> > > nr_raw_registers.
> > > (init_legacy_regcache_descr): Don't set nr_raw_registers or
> > > sizeof_raw_register_valid_p.
> > > (init_regcache_descr): Set nr_raw_registers and
> > > sizeof_raw_register_valid_p before calling
> > > init_legacy_regcache_descr.
> > >
>
> On a related note, before this change (2003-07-07 actually)
> mipsel-linux was completely broken. Info registers, in addition to
> printing R90, also claimed that all registers were zero. Backtraces
> broke for the same reason.
>
> I haven't tried newer mainline yet; I will today or tomorrow.
Sorry, Andrew - we're almost there but MIPS register handling is still
messed up. Take a look at "info all-registers":
(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.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-08-18 17:09 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 [this message]
2003-08-18 17:42 ` Andrew Cagney
2003-08-20 16:44 ` Daniel Jacobowitz
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=20030818170933.GA26128@nevyn.them.org \
--to=drow@mvista.com \
--cc=cagney@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