This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: Developing for Insight
- From: "Martin M. Hunt" <hunt at redhat dot com>
- To: "Liang, James" <jliang at sandia dot gov>
- Cc: "'insight at sources dot redhat dot com'" <insight at sources dot redhat dot com>
- Date: 10 Apr 2003 13:05:14 -0700
- Subject: Re: Developing for Insight
- References: <71251C7D5FB1D2119C8F0008C7A44ED103791FE6@es07snlnt.sandia.gov>
On Thu, 2003-04-10 at 12:46, Liang, James wrote:
> Hello. I am porting GDB and would like to make the port work with Insight.
> I had hoped to
> just get a the text version to work without having the work on Insight, but
> this is quickly becoming
> infeasible.
By "port" do you mean you are adding a new target to GDB? Or are you
porting it to a new host OS? Or both?
Which sources are you starting from?
> I'm only a few days into it, and I already have a case where the text
> version of GDB knows where I am
> (when I hit the where button, it shows the source files and line numbers),
> but the graphical version won't bring
> this info up in the window.
You should have gdb/gdbtk/library/help/debug.html. Take a look at
that. Set the environment variable "GDBTK_DEBUG" before running insight
then look for errors in the debug window. Add debug statements into the
tcl source as necessary.
See gdb/gdbtk/README for more information.
> What development environment did you guys use to debug the tcl code for
> Insight?
Just the internal debug window. It can trace or display the output of tcl debug statements.
>Is there a spec that tells which
> bits of Insight functionality depend on which data structures or which text
> GDB command?
Nothing more than the README file and inline comments.
Martin