RE: Developing for Insight

["Liang, James" <jliang at sandia dot gov>]

Actually, more than just the up and down buttons don't work.  That was just
an example.
I mean, I can't get Insight to track where I am in the code even though the
list command in the console works.

I can't get it to display assembly even though the disassemble command in
the console works.  I've been having some head-pounding fun.

-----Original Message-----
From: Martin M. Hunt [mailto:hunt at redhat dot com]
Sent: Monday, April 21, 2003 5:00 PM
To: Liang, James
Cc: 'insight at sources dot redhat dot com'
Subject: RE: Developing for Insight


On Mon, 2003-04-21 at 15:23, Liang, James wrote:

> 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 has always been the case in my experience.  The only target
specific information in Insight is in targetselection.itb. And you
shouldn't need to do anything to it for native ports, simulators, or
standard remote targets.

> 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.

I can't imagine why only those two buttons would be disabled. So the run
button works, you can set breakpoints, step, etc?

Martin