From: Jim Blandy <jimb@redhat.com>
To: "Xinan Tang" <xinan@tidalnetworks.net>
Cc: <gdb@sources.redhat.com>
Subject: Re: "Info reg doesn't work"
Date: Wed, 23 Jun 2004 05:05:00 -0000 [thread overview]
Message-ID: <vt21xk6ooew.fsf@zenia.home> (raw)
In-Reply-To: <KAEHILJLFHMPJPLKAFBHCEEOCBAA.xinan@tidalnetworks.net>
"Xinan Tang" <xinan@tidalnetworks.net> writes:
> After gdb is started, the following captures what was happening:
>
> _______________________________________________________
> (top-gdb) target sim
> complaining the floating point register size is wrong ...
> (top-gdb) info target
> simulator:
> (top-gdb)
> _______________________________________________________
>
> It seems in my gdb porting, the simulator was not found out. Where to
> start to debug this?
Well, start with remote-sim.c.
next prev parent reply other threads:[~2004-06-23 5:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 23:49 Xinan Tang
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 [this message]
[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=vt21xk6ooew.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=xinan@tidalnetworks.net \
/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).