From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Could the new gud changes move to a branch?
Date: 09 Apr 2004 11:52:20 -0400 [thread overview]
Message-ID: <87u0ztf8up.fsf-monnier+emacs@alfajor.local> (raw)
In-Reply-To: <m2vfk9oc6m.fsf@Majnun.local>
> I appreciate whoever is trying to make gud smarter, but unfortunately
> is stumbling over its own feet far too often. It has nearly rendered
> debugging from within Emacs impossible.
Just start `gdb --fullname <foo>' instead of the --annotate=3 default.
It will then use good ol' gud code. You can probably even change
the default to be --fullname, although I don't know offhand how to do it.
Stefan
next prev parent reply other threads:[~2004-04-09 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 7:14 Could the new gud changes move to a branch? John Wiegley
2004-04-09 9:31 ` Nick Roberts
2004-04-09 15:52 ` Stefan Monnier [this message]
2004-04-11 2:35 ` Richard Stallman
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=87u0ztf8up.fsf-monnier+emacs@alfajor.local \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/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).