🚀 go-pugleaf

Jordan Hubbard is/was working on the new xgdb, and he said to be
close to being ready, but I never saw a copy. 

In general, when something related to GNU says "Someone is working on
it" chances are it means a volunteer at one point has claimed that
s/he would do it.  Waiting for them to release something is generally
not a good idea--if you care enough about something so that you would
work on it except for such an announcement either (a) go ahead and
work on it anyway, or (b) try to figure out who it is (typically by
asking whoever said someone was working on it) and see whether it
would be worthwhile to collaborate, alpha test, etc.  

This article is my personal opinion; I don't know whether people at
the Free Software Foundation would agree and I very much doubt they
have any position as an organization.

As for the design of an X gdb, I think things like editing breakpoint
commands, source code display, etc *should* be integrated with emacs.
Why learn the "xgdb" editor when you already know emacs?  It's not
really overkill for those of us who already keep an emacs running all
the time anyway.  This is not to say that I find the existing
gdb-emacs sufficient--there is definately work to do improving it
(this would probably involve changes to emacs as well as to gdb.el,
such as providing a feature for putting a stop sign icon to the left
of code to indicate a breakpoint).  There is no reason why inspector
windows, etc, couldn't be emacs windows (emacs 19 or epoch allow you
to use multiple X windows).