From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: Re: gud breakage: ^done,changelist=[]
Date: Wed, 27 Oct 2004 14:07:50 +0200 [thread overview]
Message-ID: <m3fz40mkix.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <16767.24485.426051.737854@farnswood.snap.net.nz> (Nick Roberts's message of "Wed, 27 Oct 2004 21:43:17 +1300")
Nick Roberts <nickrob@snap.net.nz> writes:
> > I also see the flood of frames-invalid from time to time when
> > debugging emacs -- I reported that a long time ago.
> >
>
> Having looked at Jan's log, I think I know what is happening now. I think the
> problem occurs when the user enters the next gdb command before the previous
> one has finished.
I think that can explain something I now recall I've seen:
If the program is running, and I do C-x C-a C-t to set a breakpoint
things go ...
> So, in the short term, with care (albeit tedious), this problem should be
> avoidable.
The above "mistake" is easy to make.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-10-27 12:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 9:37 gud breakage: ^done,changelist=[] Jan Nieuwenhuizen
2004-10-18 11:17 ` Nick Roberts
2004-10-18 12:17 ` Jan Nieuwenhuizen
2004-10-18 12:58 ` Kim F. Storm
2004-10-18 21:22 ` Jan Nieuwenhuizen
2004-10-19 2:20 ` Nick Roberts
2004-10-27 8:43 ` Nick Roberts
2004-10-27 12:07 ` Kim F. Storm [this message]
2004-10-29 19:48 ` Nick Roberts
2004-10-29 20:34 ` Jan Nieuwenhuizen
2004-10-29 21:45 ` Stefan
2004-10-28 7:59 ` Jan Nieuwenhuizen
2004-10-19 6:13 ` 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=m3fz40mkix.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=janneke@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).