From: Stefan <monnier@iro.umontreal.ca>
Cc: Andreas Schwab <schwab@suse.de>, emacs-devel@gnu.org
Subject: Re: gdb-ui can't handle mutiple debugging sessions
Date: Sun, 12 Sep 2004 18:49:04 -0400 [thread overview]
Message-ID: <m1brgb8614.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <001001c49915$c144efe0$479460cb@h> (Nick Roberts's message of "Mon, 13 Sep 2004 10:12:35 +1200")
>> 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 don't see this as a serious regression and so far no-one else appears to
> (gdb-ui has been in CVS Emacs for almost two years now). If you
> can convince me otherwise or if others agree with you I will look at
> adding support for multiple sessions. However, I think this would be a
> major task which I could not complete till after the next release.
Do multiple sessions still work (at least as well as before) if you use
`gdb --fullname'?
What's the source of difficulty in supporting multiple sesions with gdb-ui?
My experience in removing the "only one per Emacs process" limitation of
various special modes (such as pcl-cvs) is that it's usually not that hard,
only it requires care (basically: make all the relevant variables
buffer-local in the main buffer and be careful to always select the main
buffer before reading those vars).
In Emacs-21.3, the multiple-session support in gud.el is pretty fragile:
it only works if all the GUD sessions use the same backend (i.e. all gdb,
or all dbx, or all perldb). That should be added to the TODO (which should
have a KNOWN-BUGS section).
Stefan
next prev parent reply other threads:[~2004-09-12 22:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-12 20:06 gdb-ui can't handle mutiple debugging sessions Andreas Schwab
2004-09-12 22:12 ` Nick Roberts
2004-09-12 22:49 ` Stefan [this message]
2004-09-12 23:32 ` Andreas Schwab
2004-09-12 23:44 ` Miles Bader
2004-09-13 3:17 ` Stefan
2004-09-14 1:33 ` Nick Roberts
2004-09-14 2:19 ` Kenichi Handa
2004-09-15 3:39 ` Nick Roberts
2004-09-15 4:10 ` Kenichi Handa
-- strict thread matches above, loose matches on Subject: below --
2004-09-15 13:22 Zoltan Kemenczy
2004-09-15 21:08 Nick Roberts
2004-09-15 22:05 Zoltan Kemenczy
2004-09-15 22:16 ` Stefan Monnier
2004-09-16 0:05 Zoltan Kemenczy
2004-09-16 13:58 ` Stefan
2004-09-17 4:17 ` Nick Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1brgb8614.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).