Toolbar problems with GDB mode.

[Nick Roberts <nick@nick.uklinux.net>]

Jan D. writes:

 > Hello.
 > 
 > If a break point is reached in a C file, the file is displayed and the toolbar 
 > changes to the GDB toolbar.  When quitting gdb, the toolbar does not change 
 > back.  Not even if gdb-quit is run.
 > 
 > I started GDB with M-x gdb.
 > 
 > If I use M-x gdba it restores the menu bar OK, but gdba has so many other 
 > problems, so I can't use it.
 > 

Hmm. I'm very aware that gdba doesn't auto-display complex data structures
(arrays of structures or structures with arrays in) and plan to solve that
when I can find the stamina. If you are more specific about other problems
then I will try to solve them.

 > I think (kill-local-variable 'tool-bar-map) should be run even if
 > (eq gud-minor-mode 'gdba) is false in this function (gdb-ui.el):

That will restore the toolbar but it will also kill any buffer whose name
starts with `*'. I could replace:

        (if (eq gud-minor-mode 'gdba)
with    (if (memq gud-minor-mode '(gdb gdba))

which would do what you want. However, I wrote gdb-quit for gdba and
I've not analysed what other consequences that might have.

In my opinion, M-x gdb is quite limited. I'm guessing, but I bet most
people on this list use gdb from the command line when they debug emacs.
It has quite some nifty features that make it easier to use: completion
of GDB command names, completion of user-defined procedure names, <RET>
sometimes repeats the previous command (handy for stepping through the
program or looking at a listing), readline interface etc, etc...

Nick