From: Andrew STUBBS <andrew.stubbs@st.com>
To: GDB <gdb@sources.redhat.com>
Subject: Invalid registers
Date: Mon, 11 Jul 2005 15:42:00 -0000 [thread overview]
Message-ID: <op.stq9spovo669wz@terrorhawk.bri.st.com> (raw)
Hi,
I have been having a little trouble updating from GDB 5.3 to GDB 6.3.
It used to be the case that GDB would report '*value not available*' (for
SH - I haven't checked other architectures) if the value of a register is
not known in the current stack frame. However, it no longer does this.
Since I assume it has not acquired some way to find out what that value
was, I also assume this is somehow broken.
(Note that SH already was broken in this respect for fp registers etc.)
The code to print the data, in sh-tdep.c, has not changed greatly. It
still calls frame_register_read() to discover the status of each register.
However, deep in regcache.c, the code to handle this sort of thing has
changed somewhat (indeed a few 'deprecated_...'s have got into the mix).
The result is that no register is ever marked invalid.
I cannot find out how (or where) it is supposed to know whether a register
is invalid or not. Nor can I find any relevant discussion on the subject
by googling (or I don't recognise it when I see it).
Has this problem been fixed since 6.3 or become somehow obsolete? If not,
any clues how to fix it?
Thanks
Andrew Stubbs
next reply other threads:[~2005-07-11 15:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 15:42 Andrew STUBBS [this message]
2005-07-11 15:49 ` Daniel Jacobowitz
2005-07-11 18:47 ` Marcel Moolenaar
2005-07-11 18:51 ` Daniel Jacobowitz
2005-07-11 19:08 ` Marcel Moolenaar
2005-07-12 16:16 ` Andrew STUBBS
2005-07-12 17:19 ` Marcel Moolenaar
2005-07-12 16:07 ` Andrew STUBBS
2005-07-12 17:34 ` Daniel Jacobowitz
2005-07-13 15:13 ` Andrew STUBBS
2005-07-13 15:42 ` Daniel Jacobowitz
2005-07-13 16:16 ` Andrew STUBBS
2005-07-13 20:27 ` Daniel Jacobowitz
2005-07-14 9:36 ` Andrew STUBBS
2005-07-14 14:11 ` 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=op.stq9spovo669wz@terrorhawk.bri.st.com \
--to=andrew.stubbs@st.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).