From: "Grzegorz Cieslewski" <cieslewski@hcs.ufl.edu>
To: gdb@sourceware.org
Subject: Problem with setting register value using MI interface
Date: Thu, 25 Oct 2007 17:48:00 -0000 [thread overview]
Message-ID: <7aa837f80710251047h2887f641kab9f0fcdda6ebd49@mail.gmail.com> (raw)
Hi,
I am trying to write a value to a register using MI2 interface.
Unfortunately sometimes th -var-assign command fails and gives me
error. Does any one know why is that?
GDB<< -var-create r1 * $r1
GDB>> ^done,name="r1",numchild="0",value="2140372880",type="uint32_t"
GDB>> (gdb)
GDB<< -var-info-type r1
GDB>> ^done,type="uint32_t"
GDB>> (gdb)
GDB<< -var-set-format r1 hexadecimal
GDB>> ^done,format="hexadecimal"
GDB>> (gdb)
GDB<< -var-evaluate-expression r1
GDB>> ^done,value="0x7f937f90"
GDB>> (gdb)
GDB<< -var-info-type r1
GDB>> ^done,type="uint32_t"
GDB>> (gdb)
GDB<< -var-set-format r1 hexadecimal
GDB>> ^done,format="hexadecimal"
GDB>> (gdb)
GDB<< -var-assign r1 1
GDB>> &"mi_cmd_var_assign: Could not assign expression to variable object\n"
GDB>> ^error,msg="mi_cmd_var_assign: Could not assign expression to
variable object"
GDB>> (gdb)
GDB<< set $r1=1
GDB>> &"set $r1=1\n"
GDB>> &"Cannot access memory at address 0x1\n"
GDB>> ^error,msg="Cannot access memory at address 0x1"
GDB>> (gdb)
--
=====================================================
Grzegorz Cieslewski
Research Assistant
High-performance Computing & Simulation (HCS) Research Laboratory
University of Florida, Dept. of Electrical and Computer Engineering
330 Benton Hall, Gainesville, FL, 32611-6200
Phone: (352) 392-9041
Email: cieslewski@hcs.ufl.edu
Web: www.hcs.ufl.edu
=====================================================
next reply other threads:[~2007-10-25 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 17:48 Grzegorz Cieslewski [this message]
2007-10-25 18:00 ` Vladimir Prus
2007-10-25 18:06 ` Daniel Jacobowitz
2007-10-25 18:17 ` Vladimir Prus
2007-10-26 14:31 ` Grzegorz Cieslewski
2007-10-26 14:41 ` Grzegorz Cieslewski
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=7aa837f80710251047h2887f641kab9f0fcdda6ebd49@mail.gmail.com \
--to=cieslewski@hcs.ufl.edu \
--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