From: Karl Chen <quarl@cs.berkeley.edu>
Cc: Emacs Developement List <emacs-devel@gnu.org>
Subject: Re: gud.el bug + patch
Date: Fri, 24 Mar 2006 14:57:23 -0800 [thread overview]
Message-ID: <quack.20060324T1457.lth1wwrtprg@roar.cs.berkeley.edu> (raw)
In-Reply-To: <17444.27917.156317.527964@kahikatea.snap.net.nz> (Nick Roberts's message of "Sat, 25 Mar 2006 10:05:01 +1200")
>>>>> On 2006-03-24 14:05 PST, Nick Roberts writes:
>> I found that having 'run' in .gdbinit triggers the problem;
>> this recipe should do it:
Nick> The mode works for you otherwise?
Yes, it works very well otherwise. I believe Emacs from 2006-01
worked even with the 'run' command in .gdbinit.
Nick> I can reproduce this bug. The problem arises because
Nick> the order of the initial annotations is not what Emacs
Nick> currently expects. I should be able at least to get M-x
Nick> gdba to work under these conditions. M-x gdb has the
Nick> added complication that it is used for both options
Nick> "--fullname" and "--annotate=3" and Emacs has to work
Nick> out which has been invoked from the output. Maybe at
Nick> some stage we can move the old behaviour (--fullname)
Nick> out to another command gud-gdb, say.
I guess it's more complicated than I thought; I got excited before
thinking I had solved the problem. Maybe you could use 'gdb -n'
to inhibit .gdbinit and then load .gdbinit after the necessary
Emacs gud-mode initialization.
--
Karl 2006-03-24 14:52
next prev parent reply other threads:[~2006-03-24 22:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 4:54 gud.el bug + patch Karl Chen
2006-03-24 12:59 ` Nick Roberts
2006-03-24 14:14 ` Karl Chen
2006-03-24 22:05 ` Nick Roberts
2006-03-24 22:57 ` Karl Chen [this message]
2006-03-25 0:15 ` Nick Roberts
2006-03-27 23:23 ` Karl Chen
2006-03-28 1:05 ` Nick Roberts
2006-03-28 1:15 ` Karl Chen
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=quack.20060324T1457.lth1wwrtprg@roar.cs.berkeley.edu \
--to=quarl@cs.berkeley.edu \
--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).