From: Sumit Garg <sgarg@apertonet.com>
To: gdb@sources.redhat.com
Subject: MIPS CPU register order
Date: Fri, 22 Jun 2001 10:54:00 -0000 [thread overview]
Message-ID: <9AAAF61573C83B4CB623DE3EEA4F9DBC20BD8E@nebula.apertonet.com> (raw)
Hi All,
I am working on enhancing the GDB, to process our properietory core files.
Currently I am dumping the registers in the .reg segment in the following
order.
sr, pc, lo, hi, gpreg[32], cause, fpcsr.
However, I am not sure if this is the order in which the function
read_registers(), would expect the registers to be. Can somebody pls give me
pointers to where the GDB register order for mips processors is stored.
Thanks
Sumit
next reply other threads:[~2001-06-22 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 10:54 Sumit Garg [this message]
2001-06-22 12:15 ` Daniel Jacobowitz
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=9AAAF61573C83B4CB623DE3EEA4F9DBC20BD8E@nebula.apertonet.com \
--to=sgarg@apertonet.com \
--cc=gdb@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