From: Antony KING <antony.king@st.com>
To: gdb@sourceware.org
Subject: Problem setting registers if stack point or frame pointer is 0
Date: Fri, 04 Apr 2008 02:21:00 -0000 [thread overview]
Message-ID: <47F54DAD.9070302@st.com> (raw)
Hi,
I have a problem trying to set a CPU register (using the GDB convenience
variable mechanism) if the stack pointer (SP) or frame pointer (FP) CPU
registers are 0. For example on an SH-4 device, where the FP register is
R14 and the SP register is R15, I see the following error from GDB (6.7.1):
(gdb) <commands to connect to SH-4 target>
(gdb) set $r15 = 0
(gdb) set $pc = 0xa0000000
Value being assigned to is no longer active.
(gdb)
The error is being generated by value_assign() (valops.c) in the
following code sequence:
case lval_register:
{
struct frame_info *frame;
int value_reg;
/* Figure out which frame this is in currently. */
frame = frame_find_by_id (VALUE_FRAME_ID (toval));
value_reg = VALUE_REGNUM (toval);
if (!frame)
error (_("Value being assigned to is no longer active."));
I can make the problem "go away" if I insert the following after the
call to frame_find_by_id() in the above code:
if (!frame)
frame = get_current_frame();
This solution was "suggestion" by a source comment in the implementation
of frame_find_by_id(). Is this the right solution do you think ?
(I am not familiar with the frame management of GDB so I thought I
would ask those more in the know about this aspect of GDB internals :-).
Cheers,
Antony.
next reply other threads:[~2008-04-03 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 2:21 Antony KING [this message]
2008-04-04 2:30 ` Daniel Jacobowitz
2008-04-04 11:43 ` Antony KING
2008-04-04 17:37 ` 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=47F54DAD.9070302@st.com \
--to=antony.king@st.com \
--cc=gdb@sourceware.org \
/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