public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "adam at irvine dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/13678] New: ARM: internal error (register not updated) in remote-sim.c
Date: Thu, 09 Feb 2012 20:33:00 -0000 [thread overview]
Message-ID: <bug-13678-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13678
Bug #: 13678
Summary: ARM: internal error (register not updated) in
remote-sim.c
Product: gdb
Version: 7.4
Status: NEW
Severity: normal
Priority: P2
Component: sim
AssignedTo: unassigned@sourceware.org
ReportedBy: adam@irvine.com
Classification: Unclassified
I built gdb for arm-elf and tried it on a program I built with GCC. I'm not
sure I configured things right or if the target program was built correctly,
but the gdb code looks suspicious enough that it's worth reporting anyway.
I used the commands:
gdb hello
(gdb) target sim
(gdb) load
(gdb) r
Starting program...
.../gdb/remote-sim.c:531: internal-error: Register 25 not updated
In sim/arm/wrapper.c, sim_store_register() appears to return -1 if the register
is any general register, floating-point register, or PS.
In gdb/remote-sim.c, gdbsim_store_register() calls sim_store_register() and
then displays the above-mentioned internal error if that function returns a
negative value. "What we've got here is a failure to communicate..."
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-02-09 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 20:33 adam at irvine dot com [this message]
2014-03-14 0:46 ` [Bug sim/13678] " vapier at gentoo dot org
2015-03-29 22:02 ` vapier at gentoo dot org
2015-03-29 22:09 ` vapier at gentoo dot org
2021-10-31 17:27 ` [Bug sim/13678] sim: arm: " vapier at gentoo dot org
2022-11-02 11:34 ` luis.machado at arm dot com
2022-11-02 11:55 ` nickc at redhat dot com
2022-11-02 11:56 ` nickc at redhat dot com
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=bug-13678-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).