From: Keith Seitz <keiths@redhat.com>
To: <mckennad@esatclear.ie>
Cc: Insight Maling List <insight@sources.redhat.com>
Subject: Re: External Program interaction with Insight
Date: Fri, 22 Feb 2002 07:42:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0202220734320.2777-100000@makita.cygnus.com> (raw)
In-Reply-To: <200202221417.JAA16150@mercury.franklin.com>
On Fri, 22 Feb 2002, Duane Ellis wrote:
>
> david> Is it possible to have an external programme interact with
> Insight so as to use GDB to retrieve information about
> registers and memory locations which can then be outputed to a
> file or to the external ?
>
> Yes, and no. Look specifically at the file "v850ice.c" in that case,
> GDB uses a programitic interface to the file "necmsg.dll"
Ouch! You had to bring thaqt up! (Yes, I wrote that POS...)
> Probably the easier - and slicker way is to use Tcl/Tk's built in
> socket stuff. What I'm suggesting is you setup a small 'server'
> application that responds to connections.
Even easier: write yourself a plugin to do it. I will be checking in a
slightly revised plugin build architecture to deal with building plugins
on multiple host platforms.
> this is how for example the memory dump window gets it's data to
> display. It just 'captures' the output of various commands an parses
> them.
Close enough. ;-) I'll be committing some changes to the memory window
interface which passes the memroy window's table into the C code and
filling it there. Gets us a good performance boost.
> In my simulator I used Tcl/Tk's tcp/ip socket interface to simulate a
> serial port. When things come in from the remote socket, the 'appear'
> as interrupts from the serial port, you read from the 'rx-data'
> register and you pull bytes out.
I hope you're using a safe tcl interpreter to do this, interfacing this
interpreter to insight's. It would be a little risky to allow direct
access to Insight's interp. I would love to see an interface class for
this specific purpose. (Hint, hint ;-)
> Just imagine - tunnel through a fire wall with http(s) to debug a
> problem on a remote machine... what is this world comming to.
Yeah. TCP/IP? WHat's that. We now use HTTP for everything. NFS? Bwaa haa
haa haa. Try WebDAV instead. Pretty soon we'll all have tcp ICMP!
Keith
next prev parent reply other threads:[~2002-02-22 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 3:59 David Mc Kenna
2002-02-22 6:17 ` Duane Ellis
2002-02-22 7:42 ` Keith Seitz [this message]
2002-02-22 9:30 ` Duane Ellis
2002-02-25 3:20 David Mc Kenna
2002-02-25 10:12 ` Keith Seitz
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=Pine.GSO.4.33.0202220734320.2777-100000@makita.cygnus.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=mckennad@esatclear.ie \
/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).