From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: MIPS saved register troubles
Date: Mon, 26 Jan 2004 15:56:00 -0000 [thread overview]
Message-ID: <20040126155623.GA2979@nevyn.them.org> (raw)
I spent some time fiddling with backtraces in an o32 application, using a
mips64-linux GDB, this morning. They don't work so well :) The basic
problem is the [0,NUM_REGS) hack. mips_register_raw_size reports that
register $28 is 8 bytes wide, so legacy_saved_regs_prev_register loads two
consecutive saved values into $28, and it looks like 0x7ffffe007ffffd8c ($s8
concatenated with $sp).
Fixing this is going to be ugly. Andrew, I don't suppose you have a plan to
migrate MIPS to the new frame code, thereby making all this go away?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2004-01-26 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 15:56 Daniel Jacobowitz [this message]
2004-01-26 17:07 ` Andrew Cagney
2004-01-26 17:14 ` Daniel Jacobowitz
2004-01-26 18:25 ` 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=20040126155623.GA2979@nevyn.them.org \
--to=drow@mvista.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