From: nickrob@snap.net.nz (Nick Roberts)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "emacs-pretest-bug@gnu.org" <emacs-pretest-bug@gnu.org>,
Robert Marshall <robert.marshall@tnei.co.uk>,
4375@emacsbugs.donarmstrong.com
Subject: bug#4375: 23.1.50; can't kill killed gud buffer
Date: Thu, 10 Sep 2009 09:55:47 +1200 [thread overview]
Message-ID: <19112.9315.801126.825982@totara.tehura.co.nz> (raw)
In-Reply-To: <jwvbplkqj6b.fsf-monnier+emacsbugreports@gnu.org>
> > If the release of 23.2 is imminent then I could temporarily move
> > gdb-ui.el back from EMACS_23_1_RC for the release. It also has some
> > new features, e.g. reverse debugging.
>
> Even if it's not imminent, it's likely that when it will happen many
> people will still be using older GDB releases. So it'd be good to keep
> the gdb-ui.el code for Emacs-23.2 (and include the new gdb-mi.el as
> well).
Emacs 23.1 is always an option for those using older GDB releases. Migrating
properly to GDB/MI is not an easy thing to do and I want to focus on that
rather than on compatibility with old versions of GDB. Others can work on
maintaining compatibility if they wish but it will make the code a lot more
complicated.
> BTW, as you probably already know, I really think that M-x gdb should Do
> the Right Thing, whether gdb is run with --annotate=2, --annotate=3,
> or -i=mi. I.e. it should wait to see GDB's output and then decide based
> on that output whether to use gdb-mi.el or gdb-ui.el or just gud.el.
We used to do that with "--fullname" and "--annotate=3" but that caused
problems when execution was started in the users .gdbinit file. The two
options are now invoked with separate functions (M-x gud-gdb and M-x gdb).
> > Is installing Gdb 7.0 not an option once it has been released?
>
> I don't understand this question.
I wondered what was preventing Jan from using GDB 7.0.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2009-09-09 21:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AA8BA2E.3020005@tnei.co.uk>
2009-09-08 15:08 ` bug#4375: 23.1.50; can't kill killed gud buffer Robert Marshall
2009-09-08 22:48 ` Nick Roberts
2009-09-09 7:22 ` Robert Marshall
2009-09-09 9:12 ` Nick Roberts
2009-09-09 10:41 ` Jan D.
2009-09-09 11:13 ` Nick Roberts
2009-09-09 14:41 ` Stefan Monnier
2009-09-09 21:55 ` Nick Roberts [this message]
2009-09-10 3:29 ` Stefan Monnier
2009-09-10 4:13 ` Nick Roberts
2009-09-10 9:04 ` Jan D.
2009-09-10 9:09 ` Jan D.
2009-09-10 8:57 ` Jan D.
2009-09-10 10:03 ` Nick Roberts
2009-09-10 3:09 ` Nick Roberts
2009-09-10 8:36 ` Robert Marshall
2009-09-10 3:49 ` Nick Roberts
2009-09-10 9:09 ` Robert Marshall
2009-09-10 10:08 ` Nick Roberts
2009-09-10 14:28 ` Robert Marshall
2009-09-10 21:37 ` Nick Roberts
2009-09-11 13:24 ` Robert Marshall
2009-09-10 8:45 ` bug#4375: marked as done (23.1.50; can't kill killed gud buffer) Emacs bug Tracking System
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=19112.9315.801126.825982@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=4375@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=robert.marshall@tnei.co.uk \
/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).