all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 16:13:23 +1200	[thread overview]
Message-ID: <19112.31971.580210.13808@totara.tehura.co.nz> (raw)
In-Reply-To: <jwvws47mqj4.fsf-monnier+emacsbugreports@gnu.org>

 > > Emacs 23.1 is always an option for those using older GDB releases.
 > 
 > Rather you mean "using gud-gdb is always an option for those using older
 > GDB releases" (we're talking about what to do for Emacs-23.2, so we
 > take for granted that the user will be using Emacs-23.2).
 > That might be good enough (I personally always end up using gud-gdb
 > since I've always found M-x gdb to be somewhat unreliable).

No I don't, I mean M-x gdb in Emacs 23.1 is always an option for those using
older GDB releases (although it may depend how old, gdb-ui.el is better with
6.4 and later but should work back to 5.0 from 2000).

M-x gud-gdb should work in Emacs 23.1.50 as it does in Emacs 23.1.

I don't know what you mean by unreliable, but over the years, in my
experience, M-x gdb has become more reliable.  Of course if you have a highly
customized environment, the results might be different and buffers might
appear in strange places.  If you are having problems, I would recommend
starting with gdb-many-windows nil and then the startup should be similar
gud-gdb except that you can set breakpoints/control execution in the margin
and see the breakpoint locations there.  Then you could display new buffers in
new frames, as and when needed, by using the pull down menu: GUD >
GDB-Frames-> <desired GDB buffer>.

 > > 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).
 > 
 > I know, but I still think this is a temporary workaround.  We should
 > document it well in some comments to make sure someone who wants to
 > attack the problem doesn't waste time going through the same problems
 > agains.

On the contrary, I would like to remove gud-gdb at some point in the future.

-- 
Nick                                           http://www.inet.net.nz/~nickrob





  reply	other threads:[~2009-09-10  4:13 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
2009-09-10  3:29                 ` Stefan Monnier
2009-09-10  4:13                   ` Nick Roberts [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19112.31971.580210.13808@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.