Tools to generate the ARI bug lists

[Joel Brobecker <brobecker at gnat dot com>]

> Before any initial commit, could you please go through them with a fine 
> tooth comb and eliminate anything obvious.  See 
> http://sources.redhat.com/gdb/current/ari/ for a reference.  You need to 
> at least work through Fixed (Critical), Coding and Deprecated 
> (interestingly ``register'' isn't yet listed under any of those :-)

Can you tell me how the list was generated? I have cleaned the few
instances of the "register" keyword, but would appreciate the assistance
of some tools to spot the other bad constructs.
Unfortunately, I can't find the tool that was used to produce the ari
bug files.

I tried to checkout the gdbadmin repository, but that failed, due to a
permission denied:

| cvs -z9 -d :pserver:anoncvs@sources.redhat.com:/cvs/gdbadmin co .
| cvs server: Updating .
| cvs server: failed to create lock directory for `/cvs/gdbadmin' (/cvs/gdbadmin/#cvs.lock): Permission denied
| cvs server: failed to obtain dir lock in repository `/cvs/gdbadmin'
| cvs [server aborted]: read lock failed - giving up


Thanks,
-- 
Joel