A few notes on gdb improvements that would help the GUI:

* The dprintf code here required some hacks.
  Some kind of I/O redirection capability would be helpful.
  Also this would require being able to subclass a dprintf breakpoint.
  Alternatively, a hook on a Breakpoint that is called when a
  linespec is resolved would work.  Right now you can't make a pending
  "gui dprintf".

* Some events are missing.  This means the GUI can't properly react to
  changes.  For example:
  * No "new breakpoint" event.  (And this in turn means that more
    breakpoint types must be exposed.)
    http://sourceware.org/bugzilla/show_bug.cgi?id=15620
  * No "new shared library" event.
    http://sourceware.org/bugzilla/show_bug.cgi?id=15621
  * No "new thread" event.
    http://sourceware.org/bugzilla/show_bug.cgi?id=15622
  * No "frame selection" event, e.g. when user types "up".

* There is no access to the line table
  This means we can't have the source window display which lines
  are executable and which are not
  http://sourceware.org/bugzilla/show_bug.cgi?id=15629

================================================================

Windows

assembly view (?)
breakpoint
signal handling?
data display
  special registers display?
  auto-updater?
stack
inferiors/threads
  could expand into stack?
list of files in the program
redirect gdb stdlog to a window