Re: M-x gdb troubles

[Kim F. Storm]

Stefan Monnier <address@hidden> writes:

> >> If I have a running gdb process (M-x gdb ... run), and accidentally do
> >> M-x gdb again (instead of switching to the gdb buffer), things get
> >> really messy...
> 
> >> Maybe the second M-x gdb should just switch to the current gdb buffer 
> >> if I enter the same command line as a previous gdb run.
> 
> > How about this patch. The catch form would have to be added to the other
> > debugger functions (dbx, pdb, perldb etc) to be consistent.

I haven't had time to try this.

> 
> Yuck.  I'd much rather just throw an error and be done with it.
> Let the user switch to the gdb buffer manually.
> 

Well, what if it jumped to the existing buffer and then signalled an error
(e.g. gdb already running).

I could live with that...  :-)

-- 
Kim F. Storm <address@hidden> http://www.cua.dk