From: fche@redhat.com (Frank Ch. Eigler)
To: "Vineet Sharma, Noida" <vineets@noida.hcltech.com>
Cc: gdb@sources.redhat.com
Subject: Re: simulator-gdb
Date: Wed, 04 Feb 2004 17:55:00 -0000 [thread overview]
Message-ID: <y0mwu72686w.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <1B3885BC15C7024C845AAC78314766C502FC08C4@exch-01.noida.hcltech.com>
"Vineet Sharma, Noida" <vineets@noida.hcltech.com> writes:
> I want to integrate a simulator with gdb , so how do i proceed?.
> What functiona are to be implemented, and how are invoked by gdb?
One approach is indeed the function call interface others pointed out.
For some applications, a wire protocol connection is more appropriate,
and simulators like SID, and a few of gdb's own, implement the usual
"remote" protocol across a TCP socket. This style of integration has
benefits (separate building, separate main-loop control, no GPL
licensing implications) and some costs (less automatic startup,
potentially lower performance).
- FChE
prev parent reply other threads:[~2004-02-04 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 5:16 simulator-gdb Vineet Sharma, Noida
2004-02-04 8:05 ` simulator-gdb Trilok Soni
2004-02-04 10:28 ` simulator-gdb Jon Beniston
2004-02-04 17:55 ` Frank Ch. Eigler [this message]
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=y0mwu72686w.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=vineets@noida.hcltech.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