[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Simultaneous gdb session badness
From: |
Michael Welsh Duggan |
Subject: |
Re: Simultaneous gdb session badness |
Date: |
Fri, 19 Aug 2005 00:59:03 -0400 |
User-agent: |
Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) |
Nick Roberts <address@hidden> writes:
> Michael Welsh Duggan writes:
> > Yes, I see that now. It was not obvious from NEWS, so I didn't
> > realize I needed to reread the gdb manual. (I remember reading the
> > messages covering bits of this on emacs-devel now that you brought
> > this up, but I obviously didn't read them closely enough.)
>
> The old behaviour has not changed. Perhaps NEWS should say that the new
> behaviour is the default now. (The extract that I posted earlier was from
> the Emacs manual and *not* the gdb manual. Which NEWS did you read?)
I should have said the gdb section of the Emacs manual.
> > More importantly though, if one cannot run multiple sessions without
> > using --fullname, M-x gdb should not allow you to attempt to so. It
> > would be much better for it to give an understandable error message
> > letting the user know what is going on.
>
> Sure. The problem is that Emacs has to start running gdb and receive some
> output before it knows whether its working in text mode or graphical mode.
> Currently the GUD buffer is created before gdb is run.
I would take that. It would catch the majority of cases, I think.
You'd have to start two sessions at very nearly exactly the same time
for the second to start before the first produced any output, I would
think.
--
Michael Welsh Duggan
(address@hidden)