Re: [PATCH] -data-list-changed-registers (Take 2)

[Nick Roberts <nickrob at snap dot net dot nz>]

 > > I get many failures on the testsuite, I'll try to move to a newer
 > > PC/kernel.  mi-regs.exp seems OK though.
 > 
 > What failures, in particular?

I don't think you'll want to know, I think a lot of them are kernel
related (2.4.19-16mdk).  I've attached the results below of a run with a
newer kernel (2.6.9.1-1.667 Fedora Core 3)

 > > I would like to commit my changes to -var-update (2005-05-02) sometime.
 > 
 > Sorry, I need to take another look at them.  I will try to to find the
 > time.

Thanks.

 > > I have also removed a large number of annotations from my working copy.
 > > Andrew started this process, it would be nice if he can be involved but
 > > maybe thats not possible. There are a lot of changes to the following
 > > files:
 ...
 > > 
 > > Is anyone interested?  It would be good to do this now as a release doesn't
 > > seem to be imminent.
 > 
 > I can try to take a look at it.  I do not know much about the existing
 > annotations or how people use them; that's why it takes me a long time
 > to review any patches in this area.

OK.  I'll check my changes a bit more carefully and then submit them.

I've made more changes to gdb-mi.el now (it use -data-list-changed-registers
now, for a start).  Since resources do seem to be stretched, and this is
separate code that can't break GDB, could I be given authority to check in
changes to this just this one file i.e. in MAINTAINERS:

Core: Generic components used by all of GDB
...
gdb-mi.el               nickrob@snap.net.nz 

I did suggest this once to Andrew, but it never got resolved.  It might need
an emergency general meeting and you might have to dust off a copy of the
Constitution, but in reality its no big deal.  I've been doing something like
this for Emacs for a couple of years now without problems.

Nick


FAIL: gdb.base/store.exp: var longest l; print old r, expecting -2
FAIL: gdb.base/store.exp: upvar longest l; print old r, expecting -2
FAIL: gdb.cp/annota3.exp: annotate-quit (pattern 1)
FAIL: gdb.cp/anon-union.exp: print w 1
FAIL: gdb.cp/anon-union.exp: print z 1
FAIL: gdb.cp/anon-union.exp: print w 2
FAIL: gdb.cp/anon-union.exp: print z 2
FAIL: gdb.cp/anon-union.exp: print w 3
FAIL: gdb.cp/anon-union.exp: print z 3
FAIL: gdb.java/jmisc.exp: p args
FAIL: gdb.java/jmisc1.exp: p args
FAIL: gdb.java/jprint.exp: unambiguous static call
FAIL: gdb.java/jprint.exp: single argument print call
FAIL: gdb.java/jprint.exp: double argument print call
FAIL: gdb.java/jprint.exp: virtual fn call
FAIL: gdb.java/jprint.exp: inherited static call
FAIL: gdb.java/jprint.exp: inherited virtual fn call
FAIL: gdb.mi/mi-basics.exp: environment-directory arg operation
FAIL: gdb.mi/mi-basics.exp: environment-directory empty-string operation
FAIL: gdb.mi/mi-basics.exp: environment-path dir1 dir2 operation
FAIL: gdb.mi/mi-file.exp: Getting a list of source files.
FAIL: gdb.mi/mi2-basics.exp: environment-directory arg operation
FAIL: gdb.mi/mi2-basics.exp: environment-directory empty-string operation
FAIL: gdb.mi/mi2-basics.exp: environment-path dir1 dir2 operation
FAIL: gdb.threads/thread_check.exp: breakpoint at tf
FAIL: gdb.threads/watchthreads.exp: threaded watch loop
FAIL: gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
FAIL: gdb.threads/watchthreads.exp: watchpoint on args[1] hit in thread
FAIL: gdb.threads/watchthreads.exp: combination of threaded watchpoints = 30

		=== gdb Summary ===

# of expected passes		10777
# of unexpected failures	29
# of unexpected successes	1
# of expected failures		42
# of unknown successes		6
# of known failures		38
# of untested testcases		1
# of unsupported tests		9