From: Ben Elliston <bje@redhat.com>
To: "姹 缈" <dam_wang@hotmail.com>
Cc: cgen@sources.redhat.com
Subject: Re: how to use gdb-sim?
Date: Tue, 08 Oct 2002 05:10:00 -0000 [thread overview]
Message-ID: <15778.52031.817825.350164@tooth.toronto.redhat.com> (raw)
In-Reply-To: <F120RTkLKtpQzWsfdg20000acb7@hotmail.com>
>>>>> "dam" == dam wang <gb2312> writes:
dam> As mentioned in CGEN's manual, CGEN support GDB's sim as a simulator, but I
dam> don't know how to use GDB's sim, and I can't find any document which tell
dam> me how to use it.
These are references to "GDB simulators", that is, the type of
simulators that were traditionally linked into GDB and activated using
the GDB command "target sim".
CGEN can generate both "GDB simulators" and SID simulators. GDB can
use either simulator, however -- SID has support for talking to GDB.
Ben
next prev parent reply other threads:[~2002-10-08 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 4:52 姹 缈
2002-10-08 5:10 ` Ben Elliston [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-10 3:17 姹 缈
[not found] <F174bXa69FuM2F0kWT800006edd@hotmail.com>
2002-10-09 14:07 ` Ben Elliston
2002-10-08 4:38 姹 缈
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=15778.52031.817825.350164@tooth.toronto.redhat.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dam_wang@hotmail.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).