Re: Toolbar problems with GDB mode.

["Jan D." <jan.h.d@swipnet.se>]

>>> Please don't simply kill the buffer. Always type gdb-quit before starting
>>> a new session. I'm writing documentation to say things like that and I
>>> will try to make it more robust with time.
>
>> Could you install a local kill-buffer-hook to handle that for users like 
>> Jan?
>
> Yes. I think this works best. I was trying to put it in gud-sentinel which 
> is
> called every time the process state changes. However, this is after the GUD
> buffer is killed which makes it difficult to distinguish between gdb and 
> gdba.
>
> kill-buffer-hook won't work if the user types quit in the GUD buffer but 
> this
> probably doesn't matter as quit doesn't make much sense here and just 
> leaves a
> dead buffer lying around.

Actually it does make sense.  To reconnect to an embedded target, it is
convinient to quit the debugger and later restart it.  If one is
debugging something difficult, keeping output from previous sessions
in the gdb buffer is helpful.

Note, it is usually not a quit followed directly after a restart,
but rather quit, edit some files, compile, upload new loadmodule to
the target, reboot the target, restart debugger.

Can't you both have it in a buffer delete hook and in the sentinel?

BTW, starting gdba on my embedded target which doesn't have a main
does not load any files.  It works just like M-x gdb.

	Jan D.