Re: Problem with Insight GUI mode

[Keith Seitz <keiths at redhat dot com>]

Posted to list. Read below for response.

On Tue, 2003-04-29 at 19:20, Peter Reilley wrote:
> The problem seems to the interaction between the .gdbinit file
> and the .gdbtkinit file.   I often need commands to be issued
> after the "target remote localhost:XXXX" command and the
> "load" command.   In non-GUI mode this all works quite nicely.
> If I use the .gdbinit file to connect to the remote and to issue
> some additional commands and then the "load" command, Insight
> gets into the mode where the RUN button is only highlighted.
> 
> One particular annoyance is that I need the command;
> 
> set remote memory-write-packet-size 1024
> set remote memory-write-packet-size fixed
> 
> When Insight executes these commands in my .gdbinit file it
> pops up a window asking if I really want the packet size changed.
> If I did not want it changed I would not have put it in my .gdbinit
> file!
> 
> I can almost always get to the point where the GUI works properly.
> Often this requires that I issue commands in the console window.
> I don't seem to be able to have Insight come up, set the breakpoint
> at main, run to main and stop.
> 
> Everything works perfectly in non-GUI mode.
> 
> Pete.

I could see that gdb would mess up the whole "set remote ..." thing. If
there's a warning in the code, then the GUI is going to display it. 
There may be a way to fix this. In remote.c, I see that when you set
this option, it calls the function query. Somehow GDB is supressing this
when starting up. If we find out how, Insight could be made to ignore
this, too.

Otherwise, as for fixing your other problems, I haven't heard anything
about whether "tk gdbtk_update" fixes the button problem. If it does,
you can add something like "tk after idle gdbtk_update" to your
.gdbinit. It'll error on non-Insight runs, though...

Keith

> ----- Original Message ----- 
> From: "Keith Seitz" <keiths@redhat.com>
> To: "Peter Reilley" <micrio@mv.com>
> Cc: <insight@sources.redhat.com>
> Sent: Tuesday, April 29, 2003 10:25 AM
> Subject: Re: Problem with Insight GUI mode
> 
> 
> > On Tue, 2003-04-29 at 04:33, Peter Reilley wrote:
> > > I have a problem with Insight 5.2.1 cross compiled for the ARM
> > > processor.   Insight is running on X86 Linux.   I am using Insight
> > > to connect to a remote target using Redhat's RDA.
> > 
> > [Zowie.. 5.2.1 is old, old, old. Any chance I could convince you to go
> > to 5.3 or CVS head?]
> > 
> > > When it starts up only the RUN button is enabled, all the others
> > > are grayed out.   When using Insight/GDB in this manner you
> > > cannot use the RUN command.    If I open a command window
> > > and issue a STEP command, then everything is fine, the other
> > > buttons are enabled.
> > 
> > I'm afraid I don't understand the sequence of events. When Insight is
> > initially run, only the Run button will be enabled. This is correct.
> > When you subsequently attach to a target, the other buttons should
> > become enabled.
> > 
> > Are you saying that after attaching/downloading/etc, only the run button
> > remains enabled? That's a problem :-). There are a couple of things that
> > we might be able to do to work around the problem.
> > 
> > Can you open a console window and enter the commands:
> > 
> > (gdb) tk gdb_target_has_execution
> > (gdb) tk set ::gdb_running
> > 
> > Send the results when you are attached to the target (and the buttons
> > are disabled).
> > 
> > Try doing "tk gdbtk_update". Does that enable the buttons?
> > 
> > Keith
> > 
> > 
>