From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: MIPS saved register troubles
Date: Mon, 26 Jan 2004 17:07:00 -0000 [thread overview]
Message-ID: <4015493C.4010805@gnu.org> (raw)
In-Reply-To: <20040126155623.GA2979@nevyn.them.org>
> 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).
Can you provide more details?
> 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?
I'm not so sure? BTW, you can't miss my irregular MIPS cleanups. My
current problem is:
[regression] Internal error: pc 0x400b21 in read in psymtab, but not in
symtab.
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1519
look familar?
Andrew
next prev parent reply other threads:[~2004-01-26 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 15:56 Daniel Jacobowitz
2004-01-26 17:07 ` Andrew Cagney [this message]
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=4015493C.4010805@gnu.org \
--to=cagney@gnu.org \
--cc=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