From: fche@redhat.com (Frank Ch. Eigler)
To: Zampieri Marco <in000466@students.univr.it>
Cc: <gdb@sourceware.cygnus.com>
Subject: Re: Connect 2 mips simulator..
Date: Mon, 03 Sep 2001 09:19:00 -0000 [thread overview]
Message-ID: <o57kvgw8kk.fsf@touchme.toronto.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109031739030.734-100000@delta009.sci.univr.it>
Zampieri Marco <in000466@students.univr.it> writes:
: Where I can find developer documentation to understand how the simulator
: and gdb dialog.
The primary interface between gdb and its mips simulator is an API
defined by include/remote-sim.h.
: In fact, I must know how write a little program that connect to mips
: simulator and drive its functionality.
You may accomplish this by writing a C program that uses the above API
and links to the libsim.a library.
: I search to develop a comunication system between 2 or plus mips
: simulator. This permit me to send datas between 2 or plus process
: cross-compiled for mips execute in your simulator. [...]
The gdb simulators are not designed to allow multiple instances to
coexist within a single application. So, you can accomplish what you
want by interconnecting simulators running as separate applications,
by some middleware of your own. Alternately, the existing simulator
"--memory-mapfile FILE" command line option may help, if the
interconnection between the simulators is limited to sharing some
region of target RAM.
- FChE
next prev parent reply other threads:[~2001-09-03 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 8:42 Zampieri Marco
2001-09-03 9:19 ` Frank Ch. Eigler [this message]
2001-09-06 5:44 ` Zampieri Marco
2001-09-06 6:46 ` Frank Ch. Eigler
2001-09-06 7:46 ` Zampieri Marco
2001-09-06 15:19 Frank Ch. Eigler
2001-09-07 4:37 Manganotto Filippo
2001-09-07 4:42 ` Frank Ch. Eigler
[not found] ` <Pine.LNX.4.33.0109071359470.29146-100000@delta046.sci.univr.it>
2001-09-07 7:09 ` Frank Ch. Eigler
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=o57kvgw8kk.fsf@touchme.toronto.redhat.com \
--to=fche@redhat.com \
--cc=gdb@sourceware.cygnus.com \
--cc=in000466@students.univr.it \
/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