From: "Xinan Tang" <xinan@tidalnetworks.net>
To: <gdb@sources.redhat.com>
Subject: "Info reg doesn't work"
Date: Mon, 14 Jun 2004 23:49:00 -0000 [thread overview]
Message-ID: <KAEHILJLFHMPJPLKAFBHIEDACBAA.xinan@tidalnetworks.net> (raw)
Hi
I am porting gdb (6.1) to a new target. After adding a new target that is
similar to an existing RISC 32bit architecture, I found out two problems:
1. `info register' does not work. For example, if I type in `info reg',
the content of all registers are showing ZERO except PC no matter how many
instructions are executed.
2. Gdb can start execution from _start but can not enter main.
Could someone please point to me which files I should take a look to fix
this problem? Or is there any FAQ to explain how to add a new target based
on an existing architecture.
Thanks
--Xinan
next reply other threads:[~2004-06-14 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 23:49 Xinan Tang [this message]
2004-06-15 22:42 ` Jim Blandy
2004-06-16 0:04 ` Xinan Tang
2004-06-18 4:07 ` Jim Blandy
2004-06-23 2:38 ` Xinan Tang
2004-06-23 5:05 ` Jim Blandy
[not found] <KAEHILJLFHMPJPLKAFBHAEDFCBAA.xinan@tidalnetworks.net>
2004-06-16 1:53 ` Jim Blandy
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=KAEHILJLFHMPJPLKAFBHIEDACBAA.xinan@tidalnetworks.net \
--to=xinan@tidalnetworks.net \
--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).