From: Nick Roberts <nickrob@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>, emacs-devel@gnu.org
Subject: Re: gdb-ui can't handle mutiple debugging sessions
Date: Tue, 14 Sep 2004 13:33:33 +1200 [thread overview]
Message-ID: <001101c499fa$f5fba540$949260cb@h> (raw)
In-Reply-To: m1brgb8614.fsf-monnier+emacs@gnu.org
> Do multiple sessions still work (at least as well as before) if you use
> `gdb --fullname'?
gdb -fullname *should* work as before in all respects but I won't be able to
check anything for another couple of weeks.
> 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).
The original code (gdba.el) did have buffer-local variables although I'm
not sure that multiple sessions worked. Since the mode has multiple
windows/frames for a single session I decided it was best to make
the variables global for cleaner code. Given the difficulty that I've had
controlling the display of the appropriate windows/frames just for
a single session, I still don't think that was a bad decision.
> 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).
How often would people need that kind of support?
gdb-ui needs feedback from a wider audience to find out which features are
important. Eventually it has to be replaced by a mode that uses GDB's
Machine Interface (MI) so it is really interim code.. When I started I just
didn't realise that a release would take so long.
Nick
next prev parent reply other threads:[~2004-09-14 1:33 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
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 [this message]
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='001101c499fa$f5fba540$949260cb@h' \
--to=nickrob@gnu.org \
--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).