Re: gdb-ui can't handle mutiple debugging sessions

[Andreas Schwab <schwab@suse.de>]

Stefan <monnier@iro.umontreal.ca> writes:

>>> When trying to use two debugging sessions at the same time gdb-ui gets
>>> completely confused.  As soon as I start the second session all input is
>>> sent to it, even when typed in the window of the first session.  This is a
>>> serious regression compared the old interface.
>
>> Thats right, gdb-ui can only handle one debugging session at a time. Trying
>> to run more seemed to require the code to be a lot more complex and
>> at the time only one overlay arrow was available so, in any case the old
>> interface didn't do it very well. I have always found the best way to run
>> two
>> debugging sessions at the same time is to run two versions of Emacs.
>> Whats the problem with this approach?

I do all my work in a single Emacs session.  Having to start a new
instance would mean not being able to share buffers and various history
lists, for example.

> Do multiple sessions still work (at least as well as before) if you use
> `gdb --fullname'?

Multiple sessions with --fullname also have some limitations, but they are
easily understood.  For example, trying to set a breakpoint in a source
file with C-x a SPC will send the command to the last active session,
which is usually what you want, but not always.  In general, it works
quite well.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."