This is the mail archive of the insight@sources.redhat.com mailing list for the Insight project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Developing for Insight


Martin,


I'm starting from Insight 5.3 that I downloaded from the Redhat website.

I am adding a new target to GDB.  I set the GDBTK_DEBUG environment variable
to 1, but it's not quite printing the information I'm looking for.   My
hope(maybe an unrealistic one) is that I can somehow port GDB text mode and
debug it completely in C and have it magically work with Insight.   That
way, I don't have to learn Tcl/TK or a Tcl/TK debugger to the level of
detail that I'd probably like to fix my bugs.  The problem is that it is
difficult to figure out bugs like the buttons for the GDB "up" and "down"
commands to be disabled when
the "up" and "down" commands work fine in the GDB console.

Oh well.

James

-----Original Message-----
From: Martin M. Hunt [mailto:hunt at redhat dot com]
Sent: Thursday, April 10, 2003 2:05 PM
To: Liang, James
Cc: 'insight at sources dot redhat dot com'
Subject: Re: Developing for Insight


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




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]