Re: [QUESTION ON INSIGHT 5.0 ]

Re: [QUESTION ON INSIGHT 5.0 ]

[Keith Seitz]

Takis Psarogiannakopoulos wrote:
> 
> Hello,
> 
> Before I start this e-mail I should say: I have a fully functional
> gdb-5.0 on DG/UX. That means:
> threads working fine, (info threads, info threads-status work fine
> from a normal gdb-5.0 command line). In the later case
> "info threads-status" is a new command that is initialized inside
> the target dgux-interface specific file.
> So all what I will ask below is purely about gdbtk directory.
>
> On Tue, 11 Jul 2000, Keith Seitz wrote:
> 
> > Ok, threads support in Insight is kinda lame. If threads work with gdb
> > and you can use the "info threads" command of either the command line
> > gdb or in Insight's console window, then threads should work.
> 
> Yes "info threads" works with both insight-5.0-gdb console window or
> a standard gdb-5.0. It doesnt work from the menu. I modified
> gdbtk/library process.itb and src...text.itb (only files that have
> "info thread" string inside) to --> "info threads".
> Now it come to my mind that info threads is a unique command in a
> standard insight/gdb 5.0 but for the DG/UX target "info thread" is not
> a clear command at all.
> Since here there are two different commands :
> info threads
> info threads-status
> both sharing the common part "info thread" string.
> However insight-5.0 should be clear to gdb when View->Thread List is
> requested. So, it should issue the WHOLE command "info threads"
> and not the shorter "info thread" that is ambigous for gdb-5.0
> with target native DG/UX.

Yes, you're right.  It should use "info threads" and not some
abbreviated form. I don't know why it ever did use an abbreviated form.
That never should have happened.

> 
> > You will probably need to add your target to
> > target_is_native () in gdb/gdbtk/generic/gdbtk.c.
> 
> OK.
> 
> > I believe this is the same as loading a core file, isn't it? (I have
> > never used the 'core' target...)
> 
> I also have never used the target "core" implicitly. But since I couldnt
> load any core (after I had loaded the corresponding executable) from
> the file menu I tried to set implicitly the target to core and this wasnt
> possibe. That is why I asked.
> 
> > You'll need to load the core file from the command line or the console
> > window.
> 
> Mmm. I was under the impression that insight-5.0 will be a little
> more sophisticated.

Unfortunately, Insight was originally developed as an embedded debugger,
and very little has been done with it to really make it work WELL with
native targets. There is a lot of polishing to be done.

> 
> > You simply add your new commands to gdb in the target's tdep file. See,
> > for example, _initialize_v850ice in v850ice.c, which adds a new command
> > "ice" to gdb when this target is used.
> 
> As I said this is already has been done. The question is how I will
> add new commands to the menus of insight-5.0. For example, below
> View->Threads List I would like to have one that reads "Threads Status"
> Now I couldnt find any option inside the insight-5.0 interface that
> the user can add (during runtime) new commands (= new options in
> its menus). I guess insight will keep these new commands (if this
> was possible) to its user dir/.insight file or similar.
> If this is not possible which files should I hack inside the gdbtk
> dir to do that?

Doh! Silly me. Right now, I am uncertain if there is an "easy" way to
add things to menus. We would probably need to add something like gdb's
initialize.c hack to do this. I would suggest just adding the necessary
menus and like to the toolbar directly. If you add a keyboard shortcut
for accessing any new windows, be sure to include those in
srctextwin.itb, too.

The toolbar stuff (and the menus, too) are all entangled inside
gdb/gdbtk/libary/srcbar.tcl and toolbar.tcl. Just follow what is done,
for example, with the function browser or some other window.

I think that's about it, but I may not remember everything. If you run
into any more problems, you know where to find me/us!
Keith