gud: not handing frames-invalid notification

gud: not handing frames-invalid notification

[Kim F. Storm]

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.

Re: gud: not handing frames-invalid notification

[Kim F. Storm]

Nick Roberts <nick@nick.uklinux.net> writes:

>  > 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.

I will try do make some useful logs.

> 
> What version of gdb are you using?

GNU gdb Red Hat Linux (5.3post-0.20021129.18rh)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu".


-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

gud: not handing frames-invalid notification

[Nick Roberts]

 > 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")