unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nick@nick.uklinux.net>
Cc: emacs-devel@gnu.org
Subject: gud: not handing frames-invalid notification
Date: Tue, 4 May 2004 23:44:53 +0100	[thread overview]
Message-ID: <16536.7397.31571.915765@nick.uklinux.net> (raw)
In-Reply-To: <m3u0yw6ne1.fsf@kfs-l.imdomain.dk>


 > I have noticed lately that when I run M-x gdb on emacs, sometimes the
 > gdb session runs wild sending lots and lots of frames-invalid
 > notifications.  
 > 
 > I don't see any actual handling of this notification.

The frames-invalid annotation should just be ignored now, like many other
annotation. If it is reproducible, set the variable gdb-enable-debug-log to
t, generate the frames-invalid notifications and post the value of
gdb-debug-log to emacs-devel. Below is a (normal) sample transaction.

What version of gdb are you using?

Nick


 (send "server info frame\n" gdb-frame-handler)
 (recv . "\n^Z^Zpre-prompt\n(gdb) \n^Z^Zprompt\n")
 (recv . "\n^Z^Zframes-invalid\n\n^Z^Zframes-invalid\n\n^Z^Zframes-invalid\n\n^Z^Zbreakpoint 1\n\nBreakpoint 1, \n^Z^Zframe-begin 0 0x804849f\n\n^Z^Zframe-function-name\nmain\n^Z^Zframe-args\n ()\n^Z^Zframe-source-begin\n at \n^Z^Zframe-source-file\nmyprog.c\n^Z^Zframe-source-file-end\n:\n^Z^Zframe-source-line\n38\n^Z^Zframe-source-end\n\n\n^Z^Zsource /home/nick/myprog.c:38:389:beg:0x804849f\n\n^Z^Zframe-end\n\n^Z^Zstopped\n")

  reply	other threads:[~2004-05-04 22:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04 18:46 gud: not handing frames-invalid notification Kim F. Storm
2004-05-04 22:44 ` Nick Roberts [this message]
2004-05-04 21:27   ` Kim F. Storm

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=16536.7397.31571.915765@nick.uklinux.net \
    --to=nick@nick.uklinux.net \
    --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).