From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11517 invoked by alias); 22 Feb 2002 15:42:57 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 11429 invoked from network); 22 Feb 2002 15:42:54 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 22 Feb 2002 15:42:54 -0000 Received: from makita.cygnus.com (makita.cygnus.com [205.180.230.78]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id HAA14700; Fri, 22 Feb 2002 07:42:48 -0800 (PST) Received: from localhost (keiths@localhost) by makita.cygnus.com (8.8.8+Sun/8.6.4) with ESMTP id HAA03030; Fri, 22 Feb 2002 07:42:48 -0800 (PST) X-Authentication-Warning: makita.cygnus.com: keiths owned process doing -bs Date: Fri, 22 Feb 2002 07:42:00 -0000 From: Keith Seitz X-X-Sender: To: cc: Insight Maling List Subject: Re: External Program interaction with Insight In-Reply-To: <200202221417.JAA16150@mercury.franklin.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-q1/txt/msg00142.txt.bz2 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